Why One JavaScript Stack Failed
Lenny Bogdonoff, co-founder and CTO of Milk Video, on the past, present and future of Javascript
The real lesson is that investors backed the dream of one JavaScript stack running everything, but most teams only kept the parts that solved an immediate pain. Meteor made real time updates and full stack JavaScript easier, yet the broader vision of one framework for front end, back end, and company wide standardization gave way to more modular setups, where React handled UI and separate services handled data, hosting, and infrastructure.
-
Meteor is the clearest example of the investment wave. The company raised $11.2M in 2012 and another $20M in 2015 around the idea that developers could build web and mobile apps with one JavaScript codebase, but it was later acquired in 2019, which shows the category never became a dominant control point in software.
-
What won instead was unbundling. Jamstack tools like Vercel and Netlify made deployment, CDN delivery, and serverless functions easier without forcing teams into one all in one application framework. That fit how companies actually worked, because front end teams could move faster while keeping their existing back end systems.
-
Gatsby shows where investor interest shifted. It raised a $28M Series B in 2020, but the market moved toward Next.js and server rendering, and Netlify acquired Gatsby in February 2023. The money kept flowing into developer tools, but the winners were narrower workflow products, not one framework meant to replace the whole stack.
The direction of travel is toward opinionated layers, not universal stacks. The next winners make one painful job much simpler, deploying a site, rendering pages fast, syncing content, or running search, and then plug into the rest of the stack. JavaScript remains the common language, but not the one framework that runs everything.