Most tools do, yes.

Probably “more”

There are plenty of unvaccinated people this side of the border and it seems to be a growing trend. If the government is going to intern people in close quarters then they should probably make sure to vaccinate them. I would not be optimistic about the level of medical care sick patients will have access to in this scenario.

If they paid for themselves then the DoT wouldn’t have a multibillion dollar highway budget, and that’s not even including all the state funding.

The claim wasn't they pay for themselves but that they don't generate any income. If we want to look at externalities, we'd also have to figure out how much the Iraq war cost.

That is for Capex. Govt can always easily spend Capex, but Opex has to be covered by the users, whether its roads or trains.

To preserve backwards compatibility and not require all those old sites to update, the legacy behavior would have to be the default, with opt-in for the new behavior.

That is the opposite approach. Also an option. One could also deprecate the call without parameter and force always a parameter with which behaviour. The deprecation could last enough time that those websites would have been rewritten multiple times ;)

The control interface burned into your hardware device will not have been rewritten. And it's not like you can have a flag day where everyone switches over, so the lifespan of those hardware devices isn't that relevant.

Backwards compatibility is a large part of the point of the Web.

You could version everything at whatever granularity you like, but over time that accumulates ("bug 3718938: JS gen24 code incorrectly handles Date math as if it were gen25-34", not to mention libraries that handle some versions but not others and then implicitly pass their expectations around via the objects they create so your dependency resolver has to look at the cross product of versions from all your depencies...)

There is no free lunch. A deprecation warning lasting a decade before erroring will break less that some css boxing models and strict mode in many browsers.

I seem to recall a scene from the book where a man is smoking a cigar in an office and prints out his computer output rather than reading from a screen. It was delightfully retrofuturist (or whatever the opposite of anachronistic is).

Why stop there? It’s in meat, water, mother’s milk, and newborns are even born with microplastics already in them.

Why not start with the large sources that you can personally control?

> One 2023 study published in the journal Environmental Science & Technology found that microwaving plastic food containers releases more than 2 billion nanoplastics (smaller microplastics) and 4 million microplastics for every square centimeter of the container.

https://www.prevention.com/health/a65025549/can-you-microwav...

The problem is other people/teams making PRs to your code that you then have to maintain or fix later. It’s in your interest not to half-ass the review, creating an asymmetric amount of work for you vs them.

What is the use case? It’s hard for me to think of a reason you’d want to wrap a link in a button. If you want to navigate, use an anchor. If you want to trigger JS logic, use a button with onclick handler. If you want to navigate while doing some side effect like an API call, use an anchor with onclick handler (and don’t prevent default).

Hey, leave us humanities majors out of it. Most of us have studied critical thinking skills and ethics, which could have easily been used to avoid the various geopolitical messes we’re in right now.