Hacker News Reader

Comment by Rezo | Hacker News Reader

It is highly encouraging to me that Meteor is acknowledging the larger trends in the Javascript ecosystem and promoting React to an officical frontend layer instead of doubling down on their homegrown solution. Likewise for seamless Babel integration and planning the move to official ES6 modules.

Buying into a full-stack solution like Meteor is a scary proposition; you're giving up a large amount of control for a promised big increase in immediate productivity (which I do feel Meteor delivers on). This blog post goes a long way to alleviate my fears and makes it more likely I'll use Meteor for certain future projects.

View on HN

Honestly I'm very likely to stick with Blaze for the time being, as I've found it easier to follow & understand than Angular (haven't tried React yet).

I just like the sticking with general modularity approach (that really reminds me of Ruby).

I don't think the Meteor proposition is any scarier than getting into Rails, Django, or even Laravel. You're basically trusting a growing ecosystem that will prevent you from re-inventing the wheel.

Rails, Django, and Laravel are all server-side frameworks. You could replace one with another, without having to rewrite any client code.

Meteor is all-encompassing, covering both the client and server. That means you have much less agility in terms of swapping out components, but of course its convenience is unparalleled.

Actually this has me wondering, is there anything else out there like Meteor that covers both client and server development at the same time? Maybe GWT?

Maybe Volt http://voltframework.com/ but I didn't use it and it's hardly mainstream.

> Actually this has me wondering, is there anything else out there like Meteor that covers both client and server development at the same time?

There's also Derby.js and Socketstream which arose around the same time as Meteor:

http://derbyjs.com

http://www.socketstream.org

It doesn't have to be a full stack solution.

From meteor's article about the DDP protocol [1]:

"...a mobile client written in pure Objective C, with no Meteor code, can connect to a Meteor server (say, by using the ObjectiveDDP library), and the server doesn't see it as different from any other client."

[1] https://www.meteor.com/ddp

Reply on news.ycombinator.com