ajsharp

21 ms·

331.
by ajsharp 16y ago
Sorry. Maybe I should've been more clear in the post to say that you should almost never use bundle update without arguments , which updates the entire gem dependency graph. Running that command with an argument will only resolve dependenc
332.
by ajsharp 16y ago
Agree with everything you're saying here. What happened in our situation was someone had been working on a feature branch for a few weeks, merged in to the mainline development branch (with failing tests exposing this issue, grr!), and then
333.
by ajsharp 16y ago
That's what bundle update does, with no other arguments. The other way to use it is bundle update gem-name, which will only update the gem passed in and it's dependencies.
334.
Don't ever run bundle update(optimisdev.com)
18 points by ajsharp 16y ago|17 comments
335.
by ajsharp 16y ago
I think your depiction of the ruby community is accurate. We definitely like to promote what we're doing, be it on our blogs, at conferences, on twitter, at meetups, etc. Last year at LaRubyConf, Sarah Allen called the ruby community "the p
336.
by ajsharp 16y ago
Having used graphael (really the only graphing library I've used), I can say that I like it, but I don't love it. I like how the charts looks far more than any of the other graphing/charting libraries, except for maybe highcharts. Imo, on
337.
by ajsharp 16y ago
Without reading the article, I can sum this up in two words: perceived efficiency.
338.
by ajsharp 16y ago
+1 luigi and bigfleet. The conf being in downtown Nashville (rather than at the Opryland hotel) this year is going to provide a whole different experience. Downtown Nashville is fun, fun, fun. See you all there!