This story is unavailable.

This article seems like a magpie becoming the canary in the coal mine.

This is less of a call to “fix” javascript or SPA-type-architectures, and more of a bellwether of the turn away from a trend that goes way beyond javascript and straight to the heart of open source.

Ruby on Rails preceded NodeJS as home to piles of dependencies and versioning hell.

NodeJS just continued the trend of spreading open-source thinner and thinner. Now, each little component is transparent to a developer with a solid understanding of javascript, which is a bigger crowd than the ruby crowd.

More devs means more code, more confusion, more difficulty discerning what is quality and what is not.

The work is (as it has been for over a decade) to pick the right tools as much as it is how to use them.

If you reject the principle of trends dictating development (and there is reason to do so), then you are really rejecting the core principles of open source, because more coders in the codebase means more changes to manage and more changes eventually means more breaking changes, and more difficulty for the repo owner.

“Move fast and break things” becomes “Move fast with stable infra”. Thanks to your bud, Mark Z!

Ultimately, I see this as a sort of tipping point article indicating a broader move away from open source to more stable private architectures. It’s a bit sad, but natural.