4 ms·

Apparently somebody has bigger cajones. @sbartholomew: @dhh the the Rails community has it relatively easy: http://article.gmane.org/gmane.linux.kernel/1414106

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

amalag 14y ago
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.
- steveklabnik 14y ago
  This 'stupid stuff' breaks every single new Rails app on Heroku that uses rbenv.
  - erikpukinskis 14y ago
    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?
    - steveklabnik 14y ago
      I am repeating what Heroku's Ruby platform lead said here: https://github.com/rails/rails/commit/61b91c4c55bcbd5a2ec85d6e1c67755150653dff#commitcomment-2356705 https://github.com/rails/rails/commit/61b91c4c55bcbd5a2ec85d...
      - erikpukinskis 14y ago
        You actually removed the word "new" from the middle of his sentence, which IMO changes the meaning substantially.
        steveklabnik 14y ago
        It does, yes. This is my bad. I do not use rbenv, personally. Let's see if HN will let me edit it.
efuquen 14y ago
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.
- nateberkopec 14y ago
  A very imperfect comparison, as Linus is maintaining a kernel and DHH is maintaining (the next major version of) a highly opinionated web framework.
outside1234 14y ago
its amazing anyone commits to the kernel after seeing that. i sure the hell wouldn't.
- bad_user 14y ago
  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.
- CamperBob2 14y ago
  It makes me less likely to want to commit code to the Linux kernel, but more likely to want to run it.
fingerprinter 14y ago
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!
- zem 14y ago
  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.
  - dkuntz2 14y ago
    The mail is always public... It's part of the Linux kernel newsgroup...
    - zem 14y ago
      he could always have sent that mail to Mauro privately and a toned-down version to the list.
      - dkuntz2 14y ago
        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.

amalag 14y ago

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.

steveklabnik 14y ago
This 'stupid stuff' breaks every single new Rails app on Heroku that uses rbenv.
- erikpukinskis 14y ago
  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?
  - steveklabnik 14y ago
    I am repeating what Heroku's Ruby platform lead said here: https://github.com/rails/rails/commit/61b91c4c55bcbd5a2ec85d6e1c67755150653dff#commitcomment-2356705 https://github.com/rails/rails/commit/61b91c4c55bcbd5a2ec85d...
    - erikpukinskis 14y ago
      You actually removed the word "new" from the middle of his sentence, which IMO changes the meaning substantially.
      - steveklabnik 14y ago
        It does, yes. This is my bad. I do not use rbenv, personally. Let's see if HN will let me edit it.

efuquen 14y ago

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.

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

outside1234 14y ago

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

bad_user 14y ago
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.
CamperBob2 14y ago
It makes me less likely to want to commit code to the Linux kernel, but more likely to want to run it.

fingerprinter 14y ago

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!

zem 14y ago
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.
- dkuntz2 14y ago
  The mail is always public... It's part of the Linux kernel newsgroup...
  - zem 14y ago
    he could always have sent that mail to Mauro privately and a toned-down version to the list.
    - dkuntz2 14y ago
      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.