News for hackers. Stuff that matters.
Re:Rails will Ruby-kill Meteor — on why by natural219 on Saturday November 09, 2013 @10:19PM (#6704993)
The author is missing the point.

The whole premise of Rails is convention over configuration. Build a set of tools optimized for the average application following "best practices". And guess what? Rails is still the best framework for producing the average Web application using 2006 best practices.

Now it's 2013. The average application server starts with Rails, then throws away ERB, routing, form_for, and the entire MVC lifecycle and slaps Ember on top of it. Technology has changed a lot in seven years (mobile, javascript, blah blah blah), and more importantly, it's only getting more client side

Re:Rails will Ruby-kill Meteor — on why by zinssmeister on Saturday November 09, 2013 @10:31PM (#6705022)
exactly what rails has become to me. Models and API controllers that respond_to json. The client does the rest with Backbone, handlebars, css3 animations, ...
Re:Rails will Ruby-kill Meteor — on why by pzuraq on Saturday November 09, 2013 @11:49PM (#6705276)
Same. I feel that for apps that are mostly server-side, Rails and Django are the way to go, especially CRUD apps. In the quickly emerging client-side app market, they often serve as an overly complex JSON api that requires too much configuration IMO.

While I like what Meteor is attempting to do by merging the client and server into one framework, I feel their approach is somewhat haphazard. Using it left a bad taste in my mouth, though t be fair I haven't done much beyond building a basic app for evaluation purposes. I'm currently evaluating Derby.js, and so far I'm liking it much more.

That said, convention has yet to be established for clientside apps, so either framework could fail. I do think that there is a niche for a framework that provides both the server and the client, however.

Re:Rails will Ruby-kill Meteor — on why by zinssmeister on Sunday November 10, 2013 @01:12AM (#6705502)
what I would like to see is a Rails type framework specifically geared towards building APIs. I like asset pipeline, give me that, I like gems, I like ActiveRecord, but take views, helpers and all that jazz. I will do that on the frontend thankyouverymuch
Re:Rails will Ruby-kill Meteor — on why by goldvine on Sunday November 10, 2013 @08:46AM (#6706392)
It exists. Check out the rails-api project on GitHub
Re:Rails will Ruby-kill Meteor — on why by zinssmeister on Sunday November 10, 2013 @03:51PM (#6708383)
wow this is really great. thanks for sharing.. had no idea someone was working on this already.
Re:Rails will Ruby-kill Meteor — on why by atomical on Saturday November 09, 2013 @10:44PM (#6705060)
I can't think of any sites I frequent that use Ember. Please, where is the proof? I would like to see the numbers.
Re:Rails will Ruby-kill Meteor — on why by Kerrick on Saturday November 09, 2013 @11:05PM (#6705132)
http://bustle.com/ is a wonderful example of a consumer website that uses Ember. Square's payment dashboard is a great example of a web app that uses Ember. Tilde also maintains a list of users that wish to publicize their use of Ember: http://emberjs.com/ember-users/
Re:Rails will Ruby-kill Meteor — on why by abuiles on Sunday November 10, 2013 @01:06AM (#6705479)
Also there is this blog interviewing people/companies using Ember http://emberenos.com/
Re:Rails will Ruby-kill Meteor — on why by WalterSear on Saturday November 09, 2013 @10:53PM (#6705093)
It's not just Ember, it's all the front end frameworks.
Re:Rails will Ruby-kill Meteor — on why by andyl on Saturday November 09, 2013 @10:45PM (#6705066)
It would be great if Rails had a good solution for Meteor-like real time apps.