3 ms·
I'm someone who moved to django from meteor (for work) and at first I was shocked at how similar they were, but after that I was shocked at how out-dated django
by thatgibbyguy 11y ago
I'm someone who moved to django from meteor (for work) and at first I was shocked at how similar they were, but after that I was shocked at how out-dated django seemed.
Websockets was just one of those issues so it's good to see it addressed. However, with meteor's DDP there's still no comparison. Looking ahead to Reactive GraphQL that meteor is working on, django seems to be permanently one step behind for the foreseeable future.
These are just my opinions, but overall definitely great news for django developers.
- zeemonkee3 11y agoSo does meteor support SQL backends yet (not talking unsupported plugins or whatever MDG is promising to do Real Soon Now). If it's still tightly coupled to MongoDB then there is zero chance I can see it being used for anything more serious than an MVP or hackathon project by a company with non-trivial data requirements.
- tim333 11y agoMeteor's DDP only can have it's annoyances as well. It's ok till you want to do something like upload a photo which it's not great for.
- uptownJimmy 11y agoMeteor is pretty unfit for prime time app development. They might one day hoist it over the fence, but for right now it remains a nice idea, I think. For one thing, there were some regrettable architectural decisions made from the start: MongoDB just don't cut it. If my company tried to sell apps built with Meteor and/or MongoDB to corporate clients, we'd be waiting tables and working construction for a living. But there are other issues there, perhaps even philosophical ones. I've become disheartened at what I see happening in the JavaScript arena. Change and never-ending-newness are distorting the reality field there. It's all shiny churn, frothy and irrational.