ekunazanu

> When given a choice between grade-separated level bike lanes, and an equally good road network, people overwhelmingly prefer cars.

> Bikes are a freaking _miserable_ transportation mode. Try biking in subzero temps, or during rain/snow.

Your entire argument seems to revolve around car vs bikes. I am arguing for prioritizing human-centric infrastructure over car-centric infrastructure. This simply means not prioritizing cars above other modes of transit. For urban environments (high density areas) cars are sub-optimal at best and other alternatives like rail, buses, bikes, and trams are simply better. Granted, sometimes cars are appropriate, but I would not use those minority of cases as an argument to justify having a city designed around cars.

> Another example is China, it had bikes as the main transportation mode in many cities, but it abandoned them as soon as they could.

Because Chinese cities now have better public transit. Just look at the size and ridership of their suburban rail and metro networks.

> And humans prefer cars.

No. People who do not have access to other modes of high quality transit, and are already used to cars, prefer cars.

> not sabotaging it with bike lanes and road diets

If done right, human-centric infrastructure can create much better urban environments than car-centric ones.

I don't disagree, but I still feel that JS has a relatively low attrition rate and people there are more than competent to know the limits of their tools — that it ends up being a net positive in the long run. I wish there was a way to quantify if/when the benefits outweigh the costs.

> In 2025 ocaml is hurting JS more than it helps them

Hurts them how though? Is there no other merit to OCaml other than serving (or having served) as a tool to filter out new hires?

It's more like I want my OS package manager to be handling global packages (personal preference), and there is a higher chance of it being included in official OS repositories if it is packaged as a precompiled binary with minimal dependencies.

I have nothing against npm, but having a single binary would've been a lot more trivial and convenient. Codex is heading in that direction, and I hope others do too.

This is some seriously impressive stuff.