@dhh: @jon_lemmon Why don’t you go ahead and fork rails so you can change the default gitignore file for new apps? You can call it Rails on Drama.

ROFL, DHH has cajones.

Apparently somebody has bigger cajones.

@sbartholomew: @dhh the the Rails community has it relatively easy: http://article.gmane.org/gmane.linux.kernel/1414106 … :-)

It's funny, though the comparison isn't perfect, DHH is basically doing what Linus got infuriated about here. He's making a minor change for what seems like very little gain, meanwhile breaking third party projects that rely on Rails.

A very imperfect comparison, as Linus is maintaining a kernel and DHH is maintaining (the next major version of) a highly opinionated web framework.

Typical Linus.

Linus was right, though.

And DHH was wrong.

Not a fan of the way Linus handled that, though he sure did set the tone and expectations for everyone else!

you know, while i don't talk to people like that (and especially not in public), i have considerable sympathy for linus's position there. it is clearly a deeply held philosophical belief of his that kernel changes should not break working userspace code, and here is someone who is evidently a long-standing kernel maintainer trying to blame a user app for breaking against a technically bad kernel patch.

i'm betting he made that mail public very deliberately, as a way of telling the world at large that as kernel dictator he would not tolerate his "staff" treating users like that.

The mail is always public... It's part of the Linux kernel newsgroup...

he could always have sent that mail to Mauro privately and a toned-down version to the list.

Doesn't that defeat the purpose of having a public list?

I think a big reason it's on the public list is because it should be. Linux is Linus' baby, he has every right to yell at someone for doing pretty much anything. And in this case, it was deserved. If you're going to break the first commandment of Linux development (don't break userspace), and blame the userspace for breaking, you should be reprimanded.

its amazing anyone commits to the kernel after seeing that. i sure the hell wouldn't.

The Linux kernel is one of those top open-source projects, big, old, well oiled and with lots of contributions, both from companies and individuals.

So Linus must be doing something right.

It makes me less likely to want to commit code to the Linux kernel, but more likely to want to run it.

Lol, imagine the flames if DHH had that kind of personality. People are being molly-coddled by DHH for stupid stuff like a default in .gitignore.

This 'stupid stuff' breaks every single new Rails app on Heroku that uses rbenv.

Exactly zero of the Rails apps on Heroku will break.

When you create a new app you'll need to remove a line from the autogenerated .gitignore in order to work the way you expect.

No?

I am repeating what Heroku's Ruby platform lead said here: https://github.com/rails/rails/commit/61b91c4c55bcbd5a2ec85d...

You actually removed the word "new" from the middle of his sentence, which IMO changes the meaning substantially.

It does, yes. This is my bad. I do not use rbenv, personally. Let's see if HN will let me edit it.

Mexican-beaner grammar nazi here, is "COJONES" not "CAJONES". xD

That's a spelling issue, not a grammar issue :)

Actually, it's neither: http://en.wikipedia.org/wiki/Euphemism

Does Rails not provide a way to customize the scaffolding used to make a new app, without forking?

Yes, you can using `rails new app_name -m template_name`.

But that would be way overkilled, here, because we just speak of adding a line to the .gitignore file.

If you don't know git, .gitignore is a file you're expected to edit, you put there anything you don't want to commit in the repository.

So, once again, all the trolling is about changing a default option. Which can be changed back with one line of four characters ("/bin"), in a configuration file. Change to be made only once in the whole life of your application.

It does have some features to do this, but the point is that the default operation is simply broken for many, many people. That suggests that it should not be the default.