I think it's just a case of brain drain, followed by reckless AI adoption which both drove the quality down.

All those forks turned out to be inferior projects with substantially less contributions than the originals.

It's definitely helpful to know whether a PR was AI-assisted or not and the git attribution line is a simple and effective way of communicating that.

I also recommend specifying model name and version so the maintainer knows upfront the level of slop they are dealing with.

I'm going even simpler, just bare docker with a idempotent bash wrapper.

I hope Node eventually gets a WebSocket server like Bun has.

Problem with Go is the type system is rudimentary, so you can't "restrict" AIs as well as you could in Typescript.

https://www.typescriptlang.org/tsconfig/#erasableSyntaxOnly covers them all, I strongly recommend running with that option enabled to be future-proof.

Modern Typescript does not need runtime features.

Your comment might lack explanation, but indeed the TS team has mentioned multiple times that they don't want to add any more features that require transpilation (as opposed to "dumb" type stripping and being a strict superset of JS).

IIRC they "almost" recommend against using them (the last part, I haven't researched again now).

But the usage of many features has reached a sort of point of no return, so I hope Node will go the route of making the experimental transpilation the default for TS files at some point.

Goes to show how strong the appeal of syntax is, especially enums.

To people coming from languages with enum support, it just looks so much more organized to use them, compared to union types, despite all of the (many) drawbacks.

Maybe now people can stop blaming npm and realize none of these unreviewed package ecosystem are safe.

Could that be the explanation for the recently increased token use?