4 ms·
Rails will Ruby-kill Meteor — on why
- steveklabnik 13y agoIf the author is reading, thank you for linking to the official documentation rather than a collection of random blogs.
- dogweather 13y agoYou're welcome. I want the post to be a good resource for getting the best out of Rails.
- woah 13y agoThe software framework that I use is the best because: A. B. C. D.
- adamnemecek 13y agoSeems pretty entitled. "Meteor looks very interesting, but until it supports more of the above, we’re talking apples and oranges." If only one could somehow contribute to open source projects. Oh wait... But I guess complaining and comparing a 1 year old platform with a platform that's almost 10 years old is easier.
- tmikaeld 13y agoMy exact thought as well. When you consider how incredibly fast meteor is growing compared to how RoR has grown it becomes apparent that meteor will grow past it very quickly.
- MrBra 13y agoWhen you consider a funding of $11.2 M [1], then you'll not be surprised at how things can go so incredibly fast. Please next time do your investigation homework before comparing two totally different software ecosystems. If Ruby on Rails had that much money from the beginning now you would be running the fastest, most beautifully coded/structured super-scalable real-time app in the world :) [1] http://www.meteor.com/blog/2012/07/25/meteors-new-112-million-development-budget http://www.meteor.com/blog/2012/07/25/meteors-new-112-millio...
- natural219 13y agoThe 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
- zinssmeister 13y agoexactly what rails has become to me. Models and API controllers that respond_to json. The client does the rest with Backbone, handlebars, css3 animations, ...
- pzuraq 13y agoSame. 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.
- zinssmeister 13y agowhat 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
- sgdesign 13y agoBe sure to tune in next week for "Why Go will kill both Rails AND Meteor"…
- leokun 13y agoGo is a programming language. Rails and Meteor are frameworks. Although Go does come with more web framework features than most languages (like templates and an http server), well except for PHP.
- adamnemecek 13y agoHe was joking about the absurdity of the claim in the blog post.
- MrBra 13y agoWhich, just to make things clear to new comers, is just a reply to the absurdity of the claim of the original blog post which titled "Why Meteor will kill Rails".
- dogweather 13y agoYou got it. But I didn't do too well communicating that, I think.
- calinet6 13y agoWhat the incomprehensible kind of title is that, exactly?
- dogweather 13y agoI was trying to be clever - that didn't quite work.
- joshowens 13y agoThe blog post is gone... guess that sums up the counter-argument? :)
- dogweather 13y agoWhoops - fixed. I moved my blog to a better platform and had some hiccups.