lucas.gonze at gmail.com
Wed Oct 9 13:40:52 PDT 2013
To be clear, the fact that Meteor has a back end component is a huge
advantage, and a large part of the reason why I went with Meteor instead of
Angular or Ember.
In our work this has been a win. There's much less complexity, fewer pieces
to maintain, less to learn.
On Wed, Oct 9, 2013 at 12:14 PM, <rst at ai.mit.edu> wrote:
> Lucas Gonze writes:
> > I see Angular and peers as basically the current generation of web
> > architecture. Rails+Backbone was best of breed in the last gen, PHP the
> > winner in the generation before that.
> The thing is, of the stacks you mentioned, only Meteor has a back-end
> component; Angular and Ember are client-side code only. You still
> need *something* at the back end, and while full Rails isn't
> necessarily the best choice, Rails components (ActiveRecord in
> particular) are still a reasonable choice for that part of the stack.
> FoRK mailing list
More information about the FoRK