[rglover]

Here's an example of a really simple CRUD app. To give you an idea, I literally just wrote this in the last 10 minutes.

https://gist.github.com/themeteorchef/aa48a086824d9736033d

I added some inline comments to explain how everything is tied together, but if you have questions shoot me an email/gchat! [e-mail].

If you're looking to build a quick CRUD app, Meteor would be a great candidate.

Edit: In this example, the interaction would be when I type a taco name into the field provided and click "submit," it would immediately appear in my tacos list :)

[rezistik]

I do like the choice in entity to construct.

I'm open to giving it a look, but honestly I really love ES6, React and Express. I can't think of much reason to leave them anytime soon.

I've been known to be tempted. And if it really increases productivity the way the marketing claims than I can see it's use case at the company I work for as well.

My fear is kind of two fold.

One I really like the NodeJS micro-modules/micro services architecture. I like being able to consider each entity of an application it's own application. It's really easy to scale, it's really easy to completely replace portions of the application when I want to update them.

Second, I don't like 'automagic', I found both Rails and Ember really awful for me personally. I had to constantly check the documentation to understand what is expected of each layer, and there are always so many layers.

Last question if you'll continue to indulge me. I prefer functional programming to OO, since Meteor is reactive is it safe to assume it is also geared towards a functional paradigm?

[rglover]

Re: functional programming, yes. Meteor is very agnostic to a specific pattern/structure, so you're able to organize your application however you see fit. There are definitely "automagic" functions that they give you, but it's more of a "box of legos" mindset than "build this model of this airplane and if all the parts aren't organized by the manual, you will fail."

You can bring your own way of thinking and work it into Meteor. The platform has conventions, for sure (e.g. client code vs. server code), but none that force you into a rigid way of writing your code.

Is that what you're asking (I'm not much of a programmers programmer so my terminology is spotty)?

Edit: give it a try, but if you have a preference for writing your apps: work with that. The marketing bullshit is just that: marketing. Meteor is great, but it's not for everyone or every application. Instead of getting caught up in the woo, it's helpful to play with it for an afternoon to see if it maps to your mental model of what an application should (or could) look like. If not, stick with what ya like :)