gistfile1.txt

~/Code/ember.js ‹ruby-1.9.3›  ‹master*› $ bundle && echo "fuck you giles"
Using rake (0.9.2.2) 
Using confparser (0.0.2.1) 
Using multi_json (1.0.4) 
Using execjs (1.2.13) 
Using libxml-ruby (2.2.2) 
Using faster_xml_simple (0.5.0) 
Using httpclient (2.2.4) 
Using json (1.6.5) 
Using nokogiri (1.5.0) 
Using net-github-upload (0.0.8) 
Using github-upload (0.0.2) 
Using rack (1.4.1) 
Using thor (0.14.6) 
Using rake-pipeline (0.6.0) from https://github.com/livingsocial/rake-pipeline.git (at master) 
Using rake-pipeline-web-filters (0.6.0) from https://github.com/wycats/rake-pipeline-web-filters.git (at master) 
Using sproutcore (0.0.1) from https://github.com/wycats/abbot-from-scratch.git (at master) 
Using uglifier (1.0.4) 
Using bundler (1.1.rc.7) 
Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed.
fuck you giles

I'll look into rbenv-bundler as a solution.

I said several times that Bundler is incredibly useful, and I definitely never said Rails 3 was not an improvement at all. I agree that many of the issues I raised are not of earth-shattering importance. In fact I don't believe I ever asserted otherwise. People got furious beyond words about a blog post in which I devoted at least one paragraph, maybe more, to discussing my own balls. I never thought I would have to say this, but I really think that nobody ever needs to take my balls more seriously than I do.

I actually enjoyed RJS but I avoided it for serious work of course. UJS is def better.

Your point about Rails generating the Gemfile, though, I can't agree with that. First, your solution only works when using Bundler with Rails. Second, to even be having an argument about whether or not source :rubygems should be the default when everybody knows for a fact it's the 90% use case is just an unmistakable and incontrovertible sign of severe dysfunction within the Rails community. It's just a ridiculous conversation to be having in the first place.

Q: Should the 90% use case be the default?
A: No.

And let's face it, 90% is generous. It's probably the 99% use case or more.

I even asked one of the Bundler guys on Hacker News if I could re-open an issue about making it the default, and never got a response.

For what it's worth, if you interpret DRY as some holy quest to never type the same thing twice, you're going to have a bad time.

DRY is about not having the same behavior in multiple places. It's about segregating concerns of a system into separate parts, not saving keystrokes. Those are just helpful, and a byproduct of actually being DRY. Pushing that is like pushing code to test ratios, they're nifty and sometimes good, but they're a byproduct of good testing. Anything more is merely mental masturbation.