As the video was playing I started to thing that the JS community is going full circle and we will end up back at Meteor. Lo and behold, guess who was mentioned at the end of the video:
Time to hype MeteorJS in the comments!
As for the discussed article, I have mentioned it on TWIM as well. Here is the link:
“But here’s the catch… React went through many iterations, and its lack of imposed structure led to a lot of questionable architectural decisions.” - Exactly my thoughts when I had to choose React vs Vue after Blaze. React was and still is a mess. Here, I said it. 
Wait till people figure out the strength of “vertical-slice/feature-first architecture”… 
Who knows, maybe then even Meteor skeleton apps will be updated to something smarter, that is actually utilizing all the strength of Meteor full-stack builder, using the /imports folder as it was designed to be used originally, not current api/ui nonsense… 
But I’m also a bit afraid that the hype crowd comes back here and it will again be too noisy… From the other hand, they will anyway run away later following the next big shiny thing.
I doubt that the hype crowd is going to return. Astro, Bun and others have the money to dingle shiny things. I’m hoping for a few people who can see a potential and who can help push the project forward in significant strides.
If the major points from the roadmap are done this year, then towards the end of the year we can start thinking about moving completely to NPM or doing something a bit more adventurous. Something to capture the mojo back.
Even in its current state, Meteor is very strong. With the new builder and potential further developments, including Capacitor (maybe even Electron ), as well as the upcoming Mongo oplog optimizations, Meteor’s efficiency as a full-stack framework is already impressive and could become even better.
In short, with Meteor, one person can build a fully functional app in the same time it takes a team of “expert system architects” to decide on the proper communication protocol for their Frankenstein system, which they will obviously rewrite eight times over the next few years just because… 
I’ve seen this so many times that it’s not even funny…
Omg, one of the best comments in the Youtube Video:
Coding today is making everything so abstracted I need a shovel, torch and map just to find a component that renders an icon. “Arh but it’s far easier writing unit tests”. Oh really, where are the unit tests in this project? “Oh, we don’t do unit testing. We just know we should”. 