And I work at a company who switched to “trunk-based development” but because of bureaucracy, nothing can be merged early. Big feature branches still sit waiting for months, then need a big document describing the changes and their impact, some QA team to test the new feature branch build etc. The “release management” team simply renamed the develop branch to trunk and called it trunk-based development.
The biggest problem is that now it will be mass generated with little effort. Time to abandon Google if most of the web becomes ChatGPT generated articles. Better to talk to ChatGPT directly.
Node frameworks are famous for this purely because of a lack of standard library. I feel like most languages have a standard library that balance being generic but still providing utilities of common used stuff. So a company that doesn’t want to rely on a random guy’s library can build their own with only the features they want. But with Node, any complicated feature is using a tree of hundreds of random packages that you have no idea who created them.
I have friends who work at the biggest bank in Latin America, where most backend stuff used to be Java. Nowadays all new code is written in Kotlin.