You can make up some 'critical defects' for every tool and engine in the universe. So what game engine is perfect for an 'ambitious developer' to use?

The UBI I support comes from a land value tax. Basically every citizen has an equal share of the land of the country, and rents it out to people who want to use it. If you use more than your fair share you pay in, if you use less you get paid.

In practice you don't run into these issues often. I'm annoyed when you see different function declaration conventions in the same codebase, but generally () => is used for either one line functions or inline lambdas, and function foo(){} for everything else. Nobody uses var anymore.

The implicit conversions is a definite footgun tho.

I literally bought the cheapest EV:

400 dollars for a 2012 nissan leaf with 80% battery life and 80k miles (saved from being junked.)

MA taxes and delivery made it about 1k when it was all said and done. Insurance is 400/year.

We fit 3 kid seats in the back and have replaced all our metropolitan rides with the nissan. Ostensibly we are all < 6ft tall otherwise the 3 seats wouldn't work.

Our range is 60 miles in the summer, 50 in the winter. Because of how we use it a regular 15 amp plug works for us. Any long trip is taken with our 2018 honda HRV + Thule.

I've been monitoring the usage of our gas car and financially it makes more sense for us to rent a gas car for our trips rather than pay for the ownership + insurance of our car. The math on yearly ownership of the gas car is:

555 treasury yield when selling the car (15000 * 0.05 on a 30 less 30% taxes), 1200 insurance, 200 yearly maintenance (oil changes, amortized tires...), 375 excise tax, 40 inspection

That's about 2.2k/year or about 4 weeks of rental for an SUV. We're still holding on to the gas car for the impromptu apple picking/beach day/day trip that sets us over the 50 mile radius, but zipcar could fill that void

Could you expand on the shortcomings of Node test compared to jest?

Can you elaborate on the compatibility issues you ran into, with ESM, please? Are they related to specific libs or use-cases?

Those clients could be doing a better job - when twitch starts playing an ad on the main stream, they also provide a secondary stream that shows the actual content.

If I drink 30% of a glass of water, is the glass of water empty?

The fact that the source is so small is wild. I would have expected a huge convoluted parsing library implemented in types.

On the other hand, the fact that this is even possible is more wild. Instead of replacing JS with a proper statically-typed language, we're spending all this effort turning a preprocessor's type system into a turing-complete metalanguage. Pretty soon we'll be able to compile TypeScript entirely using types.