3 ms·
While we're not a big startup, we are using Meteor in production (https://www.getsubcurrent.com https://www.getsubcurrent.com). We picked it because it enabled
by bmajz 12y ago
While we're not a big startup, we are using Meteor in production (https://www.getsubcurrent.com https://www.getsubcurrent.com).
We picked it because it enabled us to move much faster than anything we had used in the past and while it has issues that I foresee being problematic, it seems premature to optimize for them. The Meteor team is doing a great job maintaining compatibility and not forcing us developers on to make any changes to our apps as they're rolling out exciting new stuff. Granted, I did jump on when the platform was (relatively) mature late last year.
Very happy with decision so far and looking forward to building more stuff on their platform!
- erichuppert 12y agoWhat are the issues that you expect to face?
- bmajz 12y agoJust off the top of my head: 1. We will probably eventually need SQL 2. It might not make sense to be so JS heavy, especially since we are enterprise focused and may have to support older browsers for extended periods 3. General performance issues at scale that I would have with any new framework Planning on solving these problems when we hit them - for now, fast is best.
- uptownJimmy 12y agoOther folks have said this same thing, bascially, earlier in this thread, but bmajz sums it up perfectly here. Can't agree more with this. Fast is best. Meteor drastically lessens the start-from-scratch cruft that makes any other web app framework/stack so daunting to learn. If they can get support for SQL in place, watch out.