After $20,000+ in Ruby Together donations over past few years, @basecamp has canceled its membership. Can't stand behind current direction.
-
-
Even if there's a small amount of benefit in the rename, there is no way to recoup the disruption cost across the entire ecosystem.
-
Gemfile is not going away. Literally the only change is that if you have both a gems.rb and a Gemfile in the same directory,1st will be used
-
That is literally the only technical change. It is not the social impact.
-
I personally haven’t told anyone they can’t use a Gemfile — all my projects still use one. I don’t think it really needs to be a big deal
-
I don't see the point of allowing gems.rb. If both are in active use, it just creates a decision/reading cost all the time for no reason.
-
People say it helps noobs, but a world where both Gemfile and gems.rb are both in active use is worse than having to know Gemfile is ruby.
-
For better or worse, "Gemfile is ruby" is fully accommodated in development environments the world over.
End of conversation
New conversation -
-
-
Wait what? I had no idea, that's absurd!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.