3 ms·
Might as well go with the one which sparked the wave which inspired most of these. Rails is pretty much the premier MVC framework. If you are going to go MVC,
by gexla 12y ago
Might as well go with the one which sparked the wave which inspired most of these.
Rails is pretty much the premier MVC framework. If you are going to go MVC, go with Rails. If we are looking for an alternative to Rails, then we are probably looking for an alternative to MVC, and none of these mentioned choices fit the bill.
I wonder when the day will come that we finally get sick of recreating all the libraries that typically go into an MVC framework. That day, Rails will still be going strong and we will probably give up and just go with Rails.
Of all the choices mentioned, not many have been around as long as Rails. For every day that Rails survives, the stronger it becomes. The more likely it will continue while the alternatives shrivel.
One day MVC may become obsolete, but some people might still want to use an MVC framework for whatever reason. That day, Rails will be there waiting for you.
Years ago, I watched the video on how to build a blog in 10(?) minutes. Today, I can still somewhat follow that video. With many of the MVC frameworks in this list, you couldn't do that. ZF1 is not ZF2 for example. The framework was completely changed. They might as well call ZF2 by a different name. If it were called anything more interesting than "Zend Framework" then maybe it would have a different name.
Go is interesting, but the MVC web framework ecosystem has to be created, just like we did for Node. I don't even know if that will happen anytime, or ever. Maybe people are getting sick of doing that. And then you need to wait X years to see if something actually has any lasting power.
Screw it, just go with Rails.
Or Django. ;)
- BSousa 12y agoFor all the mentions of MVC in your post, you should probably realize that Rails isn't really MVC. Some of the new JS frameworks are actually MVC, but Rails it is not. (Rails is more Model2: http://en.wikipedia.org/wiki/Model2 http://en.wikipedia.org/wiki/Model2 than true MVC).
- gexla 12y agoRight, but it's a close enough match to meet his requirements. ETA: A blue collar match as opposed to an academic match. ;)
- xmonkee 12y agoI've used Laravel a lot and my very biased personal opinion is that it's hard to beat. Have you tried it?
- fat0wl 12y agoi think only people who still code RoR tend to see it as the center of the universe. others may appreciate its influence but can see that a lot of what it offered is just a convenient packaging of what is available in other languages, presented in a more inviting "DIY" form. I used to be a Rails guy & have since learned Java. There is not much I miss, if anything. I could definitely do some things faster in Rails but now... I don't know, given the task of creating a CRUD interface in Rails or Java i think i would be faster in Rails but not by a wide margin. If I had to add any side-effects/system integrations/free-form code/advanced persistence with the expectation that it will be performant & scalable -- I would be lightyears quicker in Java. The kicker for me though is that I would expect the Rails application to need a gem upgrade, security patches, server migration, or minor refactor to comply with plugin API changes at least every 6 months. I think the Java app could sit on a cloud host for a decade without any maintenance required (provided it implements pretty open specs). I mainly code node.js & client-side js for hobby projects, but am considering Dropwizard or Clojure instead of node (I only use this because my apps are pretty json heavy so I'm trying out mongodb and want to go full-stack js). I know I found it daunting to leave Rails & go to more free-form code, but now I find it really liberating & I'm not scared of much. There is a Java lib for pretty much everything. NPM is pretty well-stocked too.