4 ms·

I shunned the JS world for a while after jumping on the Meteor bandwagon a few years ago and seeing it just fizzle out to a boat load of outdated and unsupporte

I shunned the JS world for a while after jumping on the Meteor bandwagon a few years ago and seeing it just fizzle out to a boat load of outdated and unsupported dependencies. Rails was just so much more productive and easy for solo work. But recently I built a couple of services in typescript and the ecosystem seems to have stabilised a lot, my productivity was super high and I’m majorly impressed.

agumonkey 6y ago
what was your ts stack ? vue ? react ?
austincheney 6y ago
It’s almost a reflection of framework trends, which is not interesting.
vlasky 6y ago
Meteor is alive and well! Since 2015, I have been relying on it to implement a number of SaaS solutions involving real-time location tracking. In 2016, Meteor 1.3 implemented full support for the NPM ecosystem. As a result, people switched to using NPM packages directly (where possible) instead of older Atmosphere packages. This common misconception of outdated dependencies may be the result of non-Meteor users browsing the atmosphere website and seeing many old packages.
franklyt 6y ago
Rails is still great for a project between the sizes of small and large, the former and latter of which will benefit from tools with a lighter touch (like Go), in my opinion.