4 ms·
There must be a reason though why a lot of companies are actually using this stack these days with SPAs and it seems like front-end is kind of merging with back
by kirso 5y ago
There must be a reason though why a lot of companies are actually using this stack these days with SPAs and it seems like front-end is kind of merging with back-end by using the server-side rendering and server-less DBs with Prisma for instance?
Its actually just interesting to observe.
I am a complete newbie but curious what are the seniors here think about this trend overall.
Meteor had to be sold in the end since they didn't get the adoption. But the "JAM-stack-ish" frameworks do get that adoption recently at least based on the funding rounds (kind of half serious here).
- dham 5y agoI just take that as a difference in the times. Meteor was from another era in development. We mainly did server side stuff and used backbone, knockout etc to do more complex interactions. Or just used javascript/jquery. Why would I use Meteor when I had Rails, Django, etc that was much more mature. It's different now because developers like more pain these days. A lot of developers say that it's because the customer demands more, the interactions need to be better. None of that is the case in reality. The customer doesn't really care and at the end of the day most of these frontend framework users produce a worse experience unfortunately. High CPU, uncaught errors, poor messages, optimistic update bugginess, etc.
- danjac 5y agoIIRC Meteor also shot itself in the foot by using MongoDB as the default storage, at a time when there was deep (deserved) scepticism about the reliability of MongoDB.