5 ms·
Meteor is by far my favorite new platform for side projects. I love how easy it is to get something up and running, the integrated build system and the simplici
by evo_9 12y ago
Meteor is by far my favorite new platform for side projects. I love how easy it is to get something up and running, the integrated build system and the simplicity of deploying your projects to a meteor host.
I wish there was an easy way to use a different database although I get it, it's part of what makes Meteor so easy get something up and running quickly.
My gut is that if Meteor weren't solely tied to MongoDB and instead had an easy way to switch to Firebase, Parse, etc this platform would really take off.
- primigenus 12y agoYou aren't tied to MongoDB. You can switch to Firebase (https://atmospherejs.com/mrt/firebase https://atmospherejs.com/mrt/firebase) or Parse or even REST APIs if you want. Someone is even writing a reactive MySQL driver (https://github.com/numtel/meteor-mysql https://github.com/numtel/meteor-mysql).
- uptownJimmy 12y ago1. The fact that one must hack together Meteor with anyting other than MongoDB effectively makes it "tied to MongoDB". Most people who want to engage in this level of hackery in their spare time would, I think, just ignore Meteor and dive straight into some version of the MEAN stack. 2. Because that's the whole point of Meteor: that it doesn't require the same level of server-side savviness and hackery that server-side JavaScript usually requires. Meteor is trying to be something like Rails, where the barriers to entry are not quite so prohibitive for quite so many aspiring developers. 3. Meteor must have official support for one (or more) of the SQL db's in order to take off. That's not all it needs, but it's a big one. I'm interested in seeing how SQL support is implemented, and I assume we're talking some sort of ORM, but we'll see.
- polysaturate 12y agoCompletely agreed. Without real proper officially supported SQL db connectors, I don't think meteor will really take off. I say this as someone who has used it and like a lot of the features. I just can't see myself taking something to production on mongoDB. Also, now that the meteorJS codebase is stabilizing, I think it may be time for some conventions to mature around it. Right now, it's essentially the wild west of JS.
- brentjanderson 12y agoAgreed as well, with the one qualifier - "yet". It was not very long ago that Meteor lacked something as simple as authentication and method protections. While it's not clear when some of these features will arrive 100%, they will come eventually through a community-driven effort or through an officially sponsored implementation.
- evo_9 12y agoYeah the lack of SQL db connectors is really surprising for a 1.0 platform; I'm sure it's going to be tricky to implement that so I give them a bit of pass on that front. The lack of out of the box other NoSQL options is puzzling though because NoSQL db's are a lot close to each other than pure SQL is. And given the general disdain for MongoDB these days, it seems that uncoupling from that dependency would be a high priority. I'm sure there are plenty people on HN that simply won't even give it the time of day because of MongoDB.
- nathan-muir 12y agoSQL Support: You can query data from SQL; just include necessary NPM driver and you're away. It wont be "Realtime" though. Other NoSQL Support: The realtime driver is the problem here. Meteor creates "live queries" by tailing the MongoDB oplog. This works in part because "Minimongo" a javascript based mongo query engine can examine the oplog and determine what does & doesn't match a live query. To support another NoSQL solution, this huge engineering effort would need to be reproduced. To support "Realtime" SQL, they'd need to hook in to something like PostgreSQL 9.4's logical replication, and have a javascript based query-compiler & interpreter. (Or provide a mongo-like interface to SQL.) Not impossible, but not easy by all means. I somewhat agree with the Grandparent (re: Firebase/Parse) - However, I'd like to see the Meteor team have their own realtime database; as the realtime paradigm changes how a lot of it would be built.
- nathan-muir 12y agoWhat would be your hesitations taking mongoDB into production? Personally, the lack of transactions & ACID compliance bother me - but Mongo 3.0 (Coming in March) should alleviate those concerns. [1] [1] http://www.mongodb.com/blog/post/announcing-mongodb-30 http://www.mongodb.com/blog/post/announcing-mongodb-30
- wfleming 12y agoDitto: so much about Meteor just makes the day-to-day work of building something a real pleasure compared to other tools. For me, the thing really holding it back from more serious work is that I've had real problems getting testing to work well: Velocity[1] has had a bunch of problems for me. I hope things like the focus on MongoDB and the lack of good automated testing tools are just because Meteor is still fairly immature. It could be a really good tool for a lot of use-cases. [1]: http://velocity.meteor.com http://velocity.meteor.com
- kbd 12y agoThe lack of a testing story for Meteor was what really stalled my side project with it. Since then, Velocity has become the official testing framework but I haven't gotten the chance to dig into it. I'm disappointed to hear you've had a bunch of problems with it, as I was hoping all my testing problems would be solved next time I returned to Meteor.
- tlianza 12y agoOne thing I was surprised to run into is how basic CRUD operations don't have an out-of-the-box solution, like they did even with Rails many years ago. When I read the "Discover Meteor" guide and they got to the part about handling submit buttons by writing jQuery handlers with e.preventDefault and all that, I was really surprised. Similarly I didn't see obvious, baked-in solutions to validation, or sharing templates between "edit" and "create" situations. Then, there's the built-in Meteor accounts stuff, which does not make it easy to create an admin page for users, which again I expected to be a straightfoward task. And, not only that, but once you do start to build that you read more-and-more about how allowing the client to make certain modifications is insecure, and so you should start pushing things back to Meteor methods... Anyway, a lot of this stuff has given me pause. I love the runtime speed, but the speed of getting something up and running (in terms of dev time) seems considerably slower than the equivalent in Rails, particularly around basic CRUD operations that you just need to get out of the way before you can build the more interesting stuff.
- dadair 12y agoWhile not baked into the framework itself, I've found a few repositories that aim to make CRUD a bit easier: https://github.com/aldeed/meteor-autoform/ https://github.com/aldeed/meteor-autoform/ https://github.com/aldeed/meteor-simple-schema/ https://github.com/aldeed/meteor-simple-schema/