A weird thing: on the hacker news page, in firefox mobile, all the visited links are grey, but the link to this blog post won't turn grey even when visited.
"you shouldn't be starting a high speed pursuit over a seat belt violation, or for someone going 5 over the speed limit"
That would indeed be dumb, but once somebody dumb has decided to do that they're guilty of something much more serious and the car chase is completely justified.
Mine (Civic '19) applies it if your seatbelt is fastened when you turn off the motor. Otherwise it doesn't.
I think there's a "don't do automatic stuff unless the driver is wearing their seatbelt" rule.
I guessed the term Chat Control had to be made up by opponents of the legislation, so searched for the real name.
The official name of the legislation is:
“Proposal for a Regulation of the European Parliament and of the Council laying down rules to prevent and combat child sexual abuse” (COM/2022/209 FINAL).
It is often referenced more simply as the “Child Sexual Abuse Regulation” (CSA Regulation).
Good, where do we start our "Proposal for a Regulation of the European Parliament and of the Council laying down rules to prevent and combat mass surveillance and protect children from authoritative abuses through legislative threats on their fundamental right to grow in democracy"?
The original repo is about using a subset of a language to compare language implementations. I can see the point in that. But language benchmarks like this are incredibly useless and very easy to get wrong anyway. For example it you actually cared about performance for the bounce example you would never write it like this in C. Bouncing 100 balls in a loop 50 times with 4 ifs just tests the branch predictor. There is nothing to learn from this in practice.
Respectfully disagree. This is a compiler engineering tool backed by peer-reviewed research (DLS'16, 112+ citations) and used in 30+ academic publications across PLDI, OOPSLA, and ECOOP. It requires understanding controlled experimental methodology and compiler optimization theory to interpret correctly. Perhaps that context clarifies its purpose. The goal is to assess compiler effectiveness for a common set of core language abstractions (objects, closures, arrays), not to represent application-level performance or claim that production C code would be written this way. Your "branch predictor" criticism actually validates the benchmark's design: if different language implementations handle the same branching patterns with dramatically different performance, that reveals genuine differences in compiler designs.
> those who spend a lot of time in prison seem to come out worse and reoffend. How is that helpful?
You're implying that imprisonment makes people offend more - perhaps the simpler explanation is that most criminals will commit crimes when they get the chance, especially prolific criminals. Prison takes them off the streets and stops them victimising more people - this is helpful.
reply