News for hackers. Stuff that matters.
Re:What the hell is happening to rails? by latch on Monday June 13, 2011 @08:02PM (#2651249)
I spent the end of last year doing Java/Struts. Felt like time travelling back to 2002. Back when I knew PHP, versions increased, but nothing really changed for years and years (I'd be surprised if it was much different today). The .NET folk will tell you how great ASP.NET MVC is, but they live in their own world - a new view engine doesn't close the gap which exists between it and more progressive MVC frameworks.

The point? If you want stagnant frameworks there's plenty to pick. A lot of them aren't easier to learn, but none of them require you to keep learning. This is great because it tends to attract all the programmers you want to avoid into obvious communities.

Re:What the hell is happening to rails? by kenjackson on Monday June 13, 2011 @08:53PM (#2651382)
If you want stagnant frameworks there's plenty to pick.

There's a difference between stagnant and growing in the right direction. I think the author believes that RoR is moving away from what many thought was one of its core pillars: The ability to go from nothing to an up and running web app quickly.

Lots of things aren't stagnant -- few things move in the right direction. I'm not saying that RoR isn't moving in the right direction, but I think you've created a strawman of sorts.

Re:What the hell is happening to rails? by latch on Monday June 13, 2011 @09:09PM (#2651419)
I dunno, I kinda got from the OP that is was more about moving too fast than moving in the wrong direction. But, OP aside, I get what you are saying.

IMO, as long as Rails is being driven by real application development, I'm happy. Compared to "enterprise" frameworks which are built in isolation from the real world, Rails movement seems more grounded in pragmatism.

Re:What the hell is happening to rails? by jshen on Monday June 13, 2011 @11:21PM (#2651681)
" The ability to go from nothing to an up and running web app quickly."

How in the world do the changes lead to a situation where you can't get an app up and running quickly? I don't see that at all.

Re:What the hell is happening to rails? by riffraff on Tuesday June 14, 2011 @02:00AM (#2651961)
I have no opinion on this, but the original article makes a few cases for this: no more ajax/javascript helpers in core, no more catch all route by default etc.
Re:What the hell is happening to rails? by jshen on Tuesday June 14, 2011 @10:59AM (#2653259)
The catch all route is there, you just have to uncomment it. It takes one second.

There are other points where the article is plain wrong to. "It used to be that you just used Prototype, now it goes to vast efforts to be agnostic." No, it switched the default to JQuery, thank god.

Re:What the hell is happening to rails? by PetrolMan on Tuesday June 14, 2011 @08:25AM (#2652688)
I just wanted to add my two cents because I'm actually just learning Rails right now. I had never messed with Ruby or Rails at all until two months ago and I've actually enjoyed how easy it is to build basic applications with Rails quite quickly.

I came from PHP and did a lot of work with CakePHP and some with Zend Framework. I found CakePHP fun to work with but often limiting. I found ZF unpleasant to work with and often just as limiting because the effort involved in doing certain simple tasks was often too much.

With Rails I was able to crank out some basic functionality quite quickly and the only hang up I've come across is learning how to create plugins. Then again, the plugins I need are often out there in the world and I could probably get away with never having to write one.

I still think Rails is incredibly easy to learn the basics of but it also is well developed and thought out leaving plenty of room for more advanced behavior without running into the same walls I feel I ran into with PHP development.

Since I started with Rails 3, I don't have any perspective on how difficult it is to keep up with the changes but I must say I'm excited about 3.1 and I don't mind having to dig into whatever information I can scrounge up to familiarize myself with it.

Re:What the hell is happening to rails? by nirvdrum on Monday June 13, 2011 @08:21PM (#2651300)
Surely there's some middle ground though, no? At what point do you have a stable core and then you just bolt things on? There's nothing stopping you from using SASS and Coffeescript with Rails 2.3.

I skipped the Rails 3 upgrade just simply because I couldn't justify the time sink. rspec made it ridiculously worse with the difference in Rails support between 1.x and 2.x. I'm guessing with Rails 3.1 coming out I'll have to upgrade just because most of the plugins I use have moved on and don't backport bugfixes.

It'd be nice to evolve an app without having to constantly wasting time on version compatibility. It's an absolute nightmare if you have any non-trivial-sized app.

Re:What the hell is happening to rails? by jamesbritt on Monday June 13, 2011 @09:01PM (#2651401)
Surely there's some middle ground though, no? At what point do you have a stable core and then you just bolt things on?

Very true. Frameworks should strive for a solid API that makes it easy for people to write add-ons, and avoid adding anything that is not essential.

Of course, one hacker's essential is another's bloat, but developers should give things a long hard look before adding stuff.

It's the reason I like Ramaze so much. Has what's needed, gets out of your way, it's easy to evolve or extend if you know Ruby, and it respects your opinions.

Re:What the hell is happening to rails? by sunchild on Monday June 13, 2011 @10:26PM (#2651573)
"I skipped the Rails 3 upgrade just simply because I couldn't justify the time sink."

This is where you lost me. I spent about 2 hours, aggregate, spent solving upgrade-related problems across a bunch of different apps.

Where is the time sink?

Re:What the hell is happening to rails? by jonnytran on Tuesday June 14, 2011 @02:05AM (#2651968)
The time sink is in migrating all the plugins/gems that either dropped support for Rails 2.x in favor of 3 (i.e. no version that supports both), or were abandoned for some other competing gem. What this means is that for any app that uses lots of plugins, it's a nightmare to upgrade to Rails 3.0, not because of Rails itself, but because it means you have to migrate all those plugins simultaneously just to preserve existing functionality.

There are entire sites like http://railsplugins.org/ to help you figure out if your plugins are Rails 3 compatible. Unfortunately, there simply aren't enough users to crowdsource the compatibility of all the plugins out there.

Re:What the hell is happening to rails? by nirvdrum on Wednesday June 15, 2011 @08:09AM (#2656739)
100% correct. The other fun one is rspec 1.x supports Rails 2.x but not Rails 3.x. spec 2.x supports Rails 3.x but not Rails 2.x. Since the Rails support was modular, I have no idea how this situation resulted. But it basically means I have to upgrade with no test suite.
Re:What the hell is happening to rails? by sunchild on Tuesday June 14, 2011 @02:52AM (#2652038)
Which gems are we talking about, specifically? If it was abandoned, then you should be replacing them anyway. Backward compatibility is vastly overrated.
Re:What the hell is happening to rails? by nirvdrum on Wednesday June 15, 2011 @08:11AM (#2656743)
Actually, it doesn't really matter if it was abandoned or not. Upgrading a large number of dependencies at once is going to create problems for any project. Hell, working out the redis-rb nightmare of an upgrade took well over a week of effort trying to coordinate with the various projects that depend on it.

But, if you think backward compatibility is vastly overrated, there's really no seeing eye-to-eye on this.

Re:What the hell is happening to rails? by rohitarondekar on Monday June 13, 2011 @08:41PM (#2651353)
You are not forced to use SASS and Coffeescript. You can just switch them off. You can also switch off the asset pipeline.
Re:What the hell is happening to rails? by nirvdrum on Monday June 13, 2011 @08:57PM (#2651388)
That wasn't the argument I was making. My argument was if those are the new technologies you want to play with, you don't need a major new Rails release. Since the opposing argument seems to be that Rails needs to keep breaking compatibility in order to keep up with the latest technologies.
Re:What the hell is happening to rails? by rohitarondekar on Monday June 13, 2011 @09:25PM (#2651459)
Actually Rails 3.1 has a lot more features then just the Asset Pipeline and SASS/Coffeescript default. This blog post lists most of them: http://weblog.rubyonrails.org/2011/5/22/rails-3-1-release-ca...

Also there are a lot of deprecated things that must have been removed in 3.1 ― TBH I haven't kept in touch with 3.1 development but I'm sure a lot more has happened besides the default switch and Asset Pipeline. :)

Basically in the end, Rails is a curated framework. It either fits your requirements or it doesn't. There is no need for it to work for "all possible" cases.

Also like I said you don't have to use the defaults. :)

Re:What the hell is happening to rails? by davidw on Tuesday June 14, 2011 @01:21AM (#2651880)
> Rails is a curated framework. It either fits your requirements or it doesn't.

"Opinionated" was the original description. "Curated" is just some buzzword that means "people look after it" rather than "automatically generated", which is, uh, pretty much going to be par for the course for a maintained framework.

Re:What the hell is happening to rails? by rohitarondekar on Tuesday June 14, 2011 @05:42AM (#2652365)
"Here's the Rails gospel: Promote good ideas and technologies. See Ajax, REST, Atom, testing. Rails is a curated set of tech choices." ― DHH

source: https://twitter.com/#!/dhh/status/58286524151775232

Re:What the hell is happening to rails? by davidw on Tuesday June 14, 2011 @05:53AM (#2652382)
DHH saying it does not make it any less of a silly buzzword. I much prefer his original "opinionated", as it much more clearly gets at the heart of what Rails is, that it doesn't try and be everything to everyone.
Re:What the hell is happening to rails? by wikyd on Tuesday June 14, 2011 @06:28AM (#2652450)
Curated does not just mean "people look after it." It also means that people make editorial choices about what belongs and what doesn't.
Re:What the hell is happening to rails? by davidw on Tuesday June 14, 2011 @07:15AM (#2652543)
So pretty much like most software ever developed?

"Opinionated" communicates the idea so much better - it means not only that yes, some choices were made, but that some of them are the result of strong opinions, and do not necessarily try and accommodate all points of view.

Re:What the hell is happening to rails? by rjbond3rd on Tuesday June 14, 2011 @09:26AM (#2652842)
Hang on while I grab my beret.
Re:What the hell is happening to rails? by vic_nyc on Tuesday June 14, 2011 @08:22AM (#2652675)
The link you posted above to the blog post describing Rails 3.1 seems to be broken.
Re:What the hell is happening to rails? by brazzy on Tuesday June 14, 2011 @04:49AM (#2652282)
his is great because it tends to attract all the programmers you want to avoid into obvious communities.

So basically you agree with point that Rails' rapid changes are making it less approachable, but see it as a good point?

Re:What the hell is happening to rails? by latch on Tuesday June 14, 2011 @05:45AM (#2652368)
I do see making something less approachable to programmers who don't want to learn good, yes.
Re:What the hell is happening to rails? by Retric on Monday June 13, 2011 @08:29PM (#2651320)
IMO, ASP.NET is a mediocre to poor framework get's by because it uses an above average language (C#) and a vary good editor (Visual Studio). Still it all comes down to the types of applications your creating. If your building yet another internal CRUD app go with ASP.NET. If you want to build the next hipmunk then Rails is probably a better option.
Re:What the hell is happening to rails? by xpaulbettsx on Monday June 13, 2011 @08:39PM (#2651346)
Are you talking about MVC or WebForms? If you're thinking of the framework where you lay out controls on a designer, you're fighting the wrong framework.
Re:What the hell is happening to rails? by bkhl on Monday June 13, 2011 @08:52PM (#2651377)
Can you elaborate more on why Rails might be a better option than ASP.NET MVC for creating "the next hipmunk"?
Re:What the hell is happening to rails? by erikpukinskis on Monday June 13, 2011 @09:30PM (#2651468)
Rails (really Ruby) has only one thing going for it, as far as I'm concerned:

The norm in the community is to actively refactor.

That's it. When the Rails folks redesign the routes system, not only does my app get cleaner, but I learn stuff about how to write a good DSL. When Blake Mizerany wrote Sinatra, not only did we all get a super simple new tool for prototyping web apps in, like, zero seconds.... but we all learned something about how far you can take the "hello world" simplification trend.

We're all trying to get better at programming. We're all trying to advance the state of the art in software design. And we're all learning from each other, and it's awesome.

In many ways it's just a microcosm of what's happening in the Open Source world at large. Node.js is teaching Ruby devs important stuff, just as the Node authors seem like they probably took a cue or two from Sinatra. It's why I left the Microsoft world years ago.

Loose federations of heterogenous interests with high incentives to integrate are so much more interesting than centralized organizations.

Re:What the hell is happening to rails? by riffraff on Tuesday June 14, 2011 @02:08AM (#2651972)
IMNSHO, the norm in the ruby community as of late as not been refactor, but rewrite.

When the rails folk redesign the route system it's not a refactoring cause a refactoring keeps functionalities unchanged, it does not add/remove/change corner cases. Which has happened in all major rails releases and some point ones.

Re:What the hell is happening to rails? by mnutt on Tuesday June 14, 2011 @10:12AM (#2652999)
It wasn't a rewrite. The point of TDD-assisted refactoring isn't to not change anything ever, it's to change things in a controlled way and prevent regressions. It was actually pretty interesting to watch carlhuda and the rails team take rails from 2.3 to 3.0.
Re:What the hell is happening to rails? by nirvdrum on Wednesday June 15, 2011 @08:18AM (#2656756)
That simply isn't true. I'd urge you to pick up a copy of Fowler's "Refactoring: Improving the Design of Existing Code."

"Refactoring" as a term was defined in that book. It has very much been diluted into "I changed some code because I think this is better," which is a shame because it has a very clear definition.

I should also note that having a test suite allows you to refactor with more confidence, but it's neither a requirement nor changes the definition at all. So a "TDD-assisted refactoring" isn't different from a "refactoring."

Re:What the hell is happening to rails? by latch on Monday June 13, 2011 @09:03PM (#2651406)
It's more productive. You get more done in a shorter amount of time. Not trivially either. Its more about the language (Ruby vs C#) than the Frameworks (in that all the cool shit the Framework lets you do is thanks to the language).

If you knew C really well, and someone said "Hey, you can be more efficient building a website in C#/ASP.NET", would you have that hard a time believing them?

Re:What the hell is happening to rails? by kenjackson on Monday June 13, 2011 @11:08PM (#2651662)
If you knew C really well, and someone said "Hey, you can be more efficient building a website in C#/ASP.NET", would you have that hard a time believing them?

I wouldn't. But if they said that I could write systems code better with Objective-C I'd say prove it.

Unfortunately whenever I see RoR people talk about ROR vs anything else, including ASP.NET MVC, they talk in broad strokes with statements like, "Obviously dynamic languages are far more productive than static ones." Or "People who program in Ruby are much better developers -- which is obvious to prove, because they program in Ruby."

Re:What the hell is happening to rails? by latch on Monday June 13, 2011 @11:52PM (#2651731)
I'm just another peon, but...

I'm a former ASP.NET MVP, a codebetter.com blogger, I wrote Foundations of Programming, I own a handful of .NET OSS libraries. Yada, yada, yada..

All of that is pretty meaningless, I'm not saying to show off (most of that stuff isn't show off worthy). However, by all accounts, I'm an expert C#/.NET programmer who's been in the thick of of any progressive .NET movement. I know C# and ASP.NET (MVP or WebForms) much, much better than I know Ruby and Rails. Yet, somehow, I'm still more efficient in RoR (and thats only getting more true). I can get as low level about this discussion as you want, it won't change my opinion.

The two big wins for me: I write a ton less code and code is easier to test (this is largely since IoC is a language feature).

Re:What the hell is happening to rails? by eropple on Tuesday June 14, 2011 @12:55AM (#2651833)
You know it's MVC, right? MVP and WebForms are the same thing.
Re:What the hell is happening to rails? by latch on Tuesday June 14, 2011 @01:53AM (#2651948)
Opps, right thanks. And no, WebForms is not an implementation of MVP...its an implementation of god knows what.
Re:What the hell is happening to rails? by city41 on Tuesday June 14, 2011 @09:54AM (#2652947)
MVP is "Microsoft Most Valuable Professional", which I believe is what he meant. I believe the later use of MVP (instead of MVC) is a typo.
Re:What the hell is happening to rails? by dstein on Tuesday June 14, 2011 @10:23AM (#2653041)
It's model-view-presenter, which is basically MVC.
Re:What the hell is happening to rails? by city41 on Tuesday June 14, 2011 @12:39PM (#2653696)
He said "I'm a former ASP.NET MVP", if a person is an MVP, then in that context it's "Most valuable professional"
Re:What the hell is happening to rails? by kenjackson on Tuesday June 14, 2011 @01:20PM (#2653848)
He also said:

I know C# and ASP.NET (MVP or WebForms) much, much better than I know Ruby and Rails.