Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

One 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.



While 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-simple-schema/




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: