I believe it's actually linked in the OP about half way down. What a crazy thing for an agent to do - to turn a minor disagreement into a maybe-crime.

Really nice explanation. When I saw the title I immediately remembered the tsoding video as well so it was nice to see you mentioning it

A very fun solitaire world where everyone can play together(ish). This is the same author as 'every uuid' [0] and the million chessboard thing [1]

[0] https://eieio.games/blog/writing-down-every-uuid/

[1] https://eieio.games/blog/one-million-chessboards/

What a great title. I never quite understood why XML took over the world and got itself baked in to everything. I guess it kind of did everything well enough compared to whatever came before? Or because it was heavily used in Java-land?

Edit to add: This is also the only time I've seen JWT used in a security comparison and come out on top! (re: not including the signature in the payload)

This isn't my field, but if I'm understanding correctly this is so cool. I love the idea of being able to unlock optimisations by formally specifying behaviour.

On a side note I chuckled at the following -

> Web browsers, for example, struggle to render modern web pages

I have a followup question. Given we have Equivalence meaning every Point is equal, is it possible to allow some small margin of error? Say if you have a pipeline where you require an exact match in the centre of the frame but can allow errors near the margin? I'm analogising with '--funsafe-math' where you might be willing to allow some errors in the pursuit of speed as long as it's fun and safe.

I'm really excited to see this sort of comparison and it's interesting to see what goes in to them. One question I do have is that I believe Wild really wants to focus on incremental linking as a feature (though it's not yet incremental I believe). So I'm not 100% sure that I understand why this sort of benchmark is worth pursuing, or maybe it's that pursuing raw performance helps in the pursuit of incremental linking?

They're pretty readable, I recommend that second one (though it leaves some questions I have unanswered). It's a good example of how latent issues with a large system can go unrecognised for a long time before a seeming unrelated change can trigger a cascading failure

One thing it doesn't make clear – the GPS card only supported the original L1 signal, which is what causes the GPS week rollover issue. The newer L2C signal has a much longer rollover period (157 years vs 19.6 years), which means no rollover until next century. If the GPS card had supported the newer L2C signal, then likely this would not have happened even if the other misconfigurations had still occurred.

Yeah I've seen plenty of kernels that start with a 2 with no forward path possible due to "we don't know how to get our driver working anymore"

Maybe the closest is 'join' similar to `",".join([...])`? If we could replace the string with an operator

I like fold too, but I can never remember foldl vs foldr, it's always backwards to what I expect somehow

https://news.ycombinator.com/item?id=49736033 may help :)

Thanks! That visual style approach works better for me, hopefully it sticks