Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Meteor vs. Angular

differential.io

Post reply on HN
Print view View original

31–35 of 35 posts

Re: Meteor vs. Angular

#31

Post by extraeee »

goldenkey wrote: post #30
tedchs wrote: post #16

Earlier quoted context omitted.

It also depends on MongoDB as your sole backend database. I played with Meteor when it came out and I concur maybe Meteor is OK for prototypes but for something production ready I'd rather just use Angular + Google App Engine + Google Cloud Endpoints.

Kind of silly that you wouldn't use MongoDB yet you'd use GAE. GAE is a turd, Google has been struggling to compete in the cloud business and failed to come out with any value. You get locked into a Heroku-like platform with awful performance, awful stability, and arcane quotas. http://www.carlosble.com/2010/11/goodbye-google-app-engine-g... http://3.14.by/en/read/why-google-appengine-sucks

Those two links are to articles written 3+ years ago. I'd be interested to see more recent experiences.

Re: Meteor vs. Angular

#32

Post by matb33 »

krrishd wrote: post #2

The thing that has me sticking with Angular over Meteor is that Angular doesn't care about your backend or infrastructure. With Meteor, I feel limited due to the tight integration of the server and client. Due to that, I feel like its harder to scale, and perhaps only suitable for prototyping.

I've used Meteor for a frontend project (websockets using wamp.ws talking to a hardware box, local databases being websql and indexeddb). Meteor is a build toolchain (minify etc) and a collection of packages, each providing a feature that you can (usually) opt in/out of. Seen this way, Meteor can be used in all sorts of ways, beyond the perceived server & client mongo-only implementation.

Re: Meteor vs. Angular

#33

Post by emgee3 »

treve wrote: post #3

Meteor is still way too magic for me. Seems great for rapid prototyping of real-time applications, and perhaps things like games... But I don't think I would feel comfortable building a large application on it. The problem space that it solves is not that hard, it just provides an extremely magical way to go about it. I imagine this makes things a lot harder to change, debug and maintain. But then I'm the type of per…

One cool thing about all of Meteor's magic is that it's quite understandable. Chris Mather's EventedMind and Arunoda's MeteorHacks are good resources for looking behind that curtain.

In my experience, once the magic becomes more of an understanding of the Meteor-y way of doing things, then debugging and maintaining isn't any harder than a more traditional architecture.

I wouldn't say that Meteor is a suitable framework for any type of app, but I would say its design is suitable for a lot more than just prototyping and games (with a pre-1.0 caveat).

Re: Meteor vs. Angular

#34

Post by tedchs »

goldenkey wrote: post #30
tedchs wrote: post #16

Earlier quoted context omitted.

It also depends on MongoDB as your sole backend database. I played with Meteor when it came out and I concur maybe Meteor is OK for prototypes but for something production ready I'd rather just use Angular + Google App Engine + Google Cloud Endpoints.

Kind of silly that you wouldn't use MongoDB yet you'd use GAE. GAE is a turd, Google has been struggling to compete in the cloud business and failed to come out with any value. You get locked into a Heroku-like platform with awful performance, awful stability, and arcane quotas. http://www.carlosble.com/2010/11/goodbye-google-app-engine-g... http://3.14.by/en/read/why-google-appengine-sucks

Thanks for the feedback. I would encourage you to note that those blog posts are from 2010 and 2009, and my understanding is the platform has improved dramatically in the ensuing 4-5 years. I'm a Linux systems engineer, but for an app where I'm not going to admin my own infrastructure, I have been happier with App Engine than other PaaS options.

Re: Meteor vs. Angular

#35

Post by goldenkey »

tedchs wrote: post #34
goldenkey wrote: post #30

Earlier quoted context omitted.

Kind of silly that you wouldn't use MongoDB yet you'd use GAE. GAE is a turd, Google has been struggling to compete in the cloud business and failed to come out with any value. You get locked into a Heroku-like platform with awful performance, awful stability, and arcane quotas. http://www.carlosble.com/2010/11/goodbye-google-app-engine-g... http://3.14.by/en/read/why-google-appengine-sucks

Thanks for the feedback. I would encourage you to note that those blog posts are from 2010 and 2009, and my understanding is the platform has improved dramatically in the ensuing 4-5 years. I'm a Linux systems engineer, but for an app where I'm not going to admin my own infrastructure, I have been happier with App Engine than other PaaS options.

No competent Linux admin would use a PaaS. I find it very hard to believe that you'd rather use GAE instead of a virtual dedicated.
Post reply on HN