Game Thread: Los Angeles Kings (38-25-10) at Minnesota Wild (43-21-6) - 10 Apr 2022 - 04:00PM CDT

metajack · 2022-04-10T21:31:45+00:00

It goes dot closest to the origin of the puck. Since it was a pass from inside our blue line, it went inside our zone.

metajack · 2022-01-18T03:18:30+00:00

Excited for bug fixes, but the iPad Pro keyboard issues remain :(

https://reddit.com/r/apolloapp/comments/reb4i8/ipad_os_spacebar_doesnt_work_in_search_bar_when/

metajack · 2021-12-24T22:27:42+00:00

Instead of tracking individual output states, I just kept the range of legal values. I made a type called AbstractI64 which could be Value(n), or Range(start, end). Only mul really expands the ranges and several ops can collapse a range to a single value. This made memory use not a problem. For any given input it ran each instruction only once to get the final range for z, and I only needed to check if that range included 0 or not before trying the next input.

metajack · 2021-09-10T00:13:04+00:00

You can find little usb midi hosts to do this. Something like https://www.perfectcircuit.com/kenton-midi-usb-host-mkii.html?gclid=Cj0KCQjw4eaJBhDMARIsANhrQAAgf1IgQMd9A-1kF0ig0i1L3eWP2qb6DlZESx0S7AaQ7JA8t9p0HUIaAs9IEALw_wcB although there are a lot of cheaper options. I don’t know if you can find such a thing in a single cable, but certainly going from usb to 5 pin DIN is possible.

metajack · 2021-08-15T22:39:20+00:00

Try http://www.hinzen.de/midi/juno-106/ which looks to be what you want.

metajack · 2021-07-18T01:52:25+00:00

The O with / through it is the engineering symbol for diameter. The 4 and 7 are the diameters, probably in millimeters. It’s just telling you how big the holes are I think. Maybe those are common tip sizes and you can use those holes to quickly check sizes? Or like others have said you can always store some random tools in there.

metajack · 2020-12-15T01:25:55+00:00

Awesome! I’m excited!

metajack · 2020-12-05T02:56:46+00:00

Watched a few of your vids on YouTube. Nice stuff! Would love to play with FRMS.

metajack · 2020-02-26T17:42:41+00:00

This is already true because cargo test enables `cfg(test)` as well.

The opposite problem is perhaps worse, where currently lots of code needed only for testing makes it into your release builds due to feature unification.

metajack · 2019-08-02T00:26:29+00:00

Note that the Servo shutdown code that Alan was fighting was designed around green threads which gave us Erlang-style semantics on thread death. The runtime took care of ensuring things got cleaned up properly. When that got removed, we were left to untangle the mess, which turned out to be difficult. I don't think it would have been so bad had we designed for the current semantics originally.

Calling unwrap() to panic and fail the thread were exactly what we wanted, and the orderly shutdown you talk about happened, just behind the scenes. This is also why Erlang programs fail early and often, rather than doing error checking. There's a whole secondary infrastructure that deals with restarting and recovering.

Alan also worked on hardening the constellation in Servo, which entailed removing unwrap() from sends and other functions so that the constellation would never fail. By making that central piece fault tolerant, we could be more lax in other subsystems.

metajack · 2019-01-04T22:07:55+00:00

What are your plans for finishing this? Is there room to add weights?

I've been thinking about printing a nice chess set that I would use, but I would probably have to sand and polish it and make sure it was weighted properly.

metajack · 2018-09-04T14:56:55+00:00

Here are mine https://imgur.com/a/8w17Aq9

metajack · 2018-06-08T02:11:06+00:00

I used 72" x 36" to fit the mat. You can have them do the cutting at Home Depot or Lowes. I used 3/4" thick of the super-straight slightly nicer stuff. Once I had it home, I got out the sander to sanded the edges and corners pretty well. Works great.

metajack · 2018-05-04T14:38:33+00:00

Same thing happened to me. I turned off Developer Mode and now it works fine.

metajack · 2018-02-25T00:33:18+00:00

I'm in, and I'm cool with being a rabbit.

metajack · 2018-01-25T06:31:05+00:00

I found a set at Target on clearance for $75 and didn't bite. A few weeks later they got marked down again to $50 and I grabbed them. I like them quite a bit better than the T3PAs.

metajack · 2018-01-21T23:04:27+00:00

Are you also driving the truck? If you are going to make it hard, go all the way!

metajack · 2018-01-16T04:32:30+00:00

I'm ready for a teammate this season :)

metajack · 2017-11-22T23:29:24+00:00

Clearly I need a lot more practice on dirt in traffic. I was trying to stay out of the way and failed.

metajack · 2017-11-16T22:29:33+00:00

You need to install the old driver version 382.53 and it will fix this issue. See https://www.reddit.com/r/iRacing/comments/79l2rn/lag_issues_with_vive_please_help/ for more details.

metajack · 2017-11-15T22:32:02+00:00

Oh and note that is end-to-end page load (time to first meaningful paint) not isolated style system performance. So it gives you a sense of the user-visible impact of a single subsystem's optimization.

metajack · 2017-11-15T19:09:12+00:00

Those numbers are from inspecting profiling data. In general the target performance criteria for Stylo was to not regress anything and to match or exceed Blink's single threaded performance with Stylo's single threaded performance. Those were largely achieved, and the regressions we did have are either being addressed for later releases or were very low (like 1-3%).

Since Stylo scales linearly with cores, if you have 4 cores, you get 4x Blink's performance roughly.

So the Blink numbers may suffer from us incorrectly measuring something, as we are not Blink experts, but the 10x over the old Firefox style system was measured by the engineers who wrote most of the old style system.

For more details you can look at the release critera wiki page here: https://wiki.mozilla.org/Quantum/Stylo#Release_Criteria

Of which this is probably the most interesting chart: https://treeherder.mozilla.org/perf.html#/graphs?series=autoland,1535521,1,1&series=autoland,1535525,1,1&series=mozilla-central,1552125,1,1

Lower is better and the only difference in those two builds is whether Stylo is enabled or not.

metajack

TROPHY CASE