After $20,000+ in Ruby Together donations over past few years, @basecamp has canceled its membership. Can't stand behind current direction.
-
Show this thread
-
Few factors: False accusations re: Google/license violations, hostile use of Bundler warnings to force pre-releases, Gemfile/gems.rb split.
4 replies 10 retweets 43 likesShow this thread -
fwiw it's disappointing to me that the decision to change the file name for Gemfile for the whole ecosystem was made so unilaterally.
2 replies 0 retweets 12 likes -
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.
3 replies 0 retweets 8 likes -
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
2 replies 0 retweets 0 likes -
That is literally the only technical change. It is not the social impact.
1 reply 0 retweets 1 like -
Replying to @wycats
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
1 reply 0 retweets 0 likes -
Replying to @segiddins
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.
2 replies 0 retweets 3 likes
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.
-
-
Replying to @wycats @segiddins
For better or worse, "Gemfile is ruby" is fully accommodated in development environments the world over.
0 replies 0 retweets 3 likesThanks. 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.