As the article says: this is not a general speed limit but an experimental speed limit for an apparently very crowded area where many kids cycle to school.
As someone whose 'normal biking speed' ist typically 30+ km/h on suitable bike lanes, I have no problems with speed limits at critical choke points.
Ah, this bit of crucial context seems to be missing from the entire rest of the discussion. Also makes what otherwise sounds like an uncharacteristically bike-hostile move actually seem fairly reasonable.
Tho tbf one still hopes that they come up with an infrastructure solution that makes it unnecessary in the long run.
I'm not sure whether the Guardian article mentioned this or another one I read: the road segment in question seems to be in the old town which makes it difficult to find an architectural solution.
It can happen in Sweden too but it is less likely to. We don't have a president, we have a prime minister with limited power. We have a stronger democracy run by coalitions instead of a single party. One jackass is not enough in Sweden.
I am all for minimalism but "If you come from one codebase to another codebase by a different team it’s close to learning a completely new language" I really don't agree. It's not that big. Just sounds like a skill issue
I switched between dozens of similar codebases over a period of 3-4 years (pre AI) when I was consulting and did multiple projects in multiple languages (well, only 1 in rust).
In my experience switching between the C# projects was always the worst. The codebase semantics diverged in ways I simply didn’t see in the Java/C++ codebases.
What's the problem with the JIT runtime? Why is rapid iteration slower with JIT? Just-in-time compilation isn't inherently slower and is normally faster than AOT for dynamic languages and even static languages that have some dynamic features like dynamic dispatch
reply