A Fresh Cup is Mike Gunderloy's software development weblog, covering Ruby on Rails and whatever else I find interesting in the universe of software. I'm a full-time software developer: most of my time in recent years has been spent writing Rails, though I've dabbled in many other things and like most people who have been writing code for decades I can learn new stuff as needed.

As of October 2016, I'm not actively looking for my next job, but I'm still happy to chat about potential opportunities. I'm not able to relocate, so unless you're in the Evansville area, I'd need a completely remote gig. I have lots of experience working remote. Prefer full-time but I wouldn't be averse to an interesting contact gig. Drop me a comment if you've got something or email MikeG1 [at] larkfarm.com.

Navigation
« Double Shot #563 | Main | Double Shot #561 »
Thursday
Oct152009

Double Shot #562

Today it would be nice to hit a few home runs.

Reader Comments (3)

Thanks for the pingback!

October 15, 2009 | Unregistered CommenterMark Richman

I'm haven't really dug into the bundler stuff yet, but anything's better than the existing system. I rewrote most of it for 2.2, and even I want to toss it out the window.

It currently works, for most of the typical usage scenarios - but there are a number of nasty edge cases that aren't practical (or possible) to work around. The one that jumps out the most is the "can't load vendor gems without loading the environment", which pops up in weird places like not being able to reliably call vendored Rake tasks or script/generate not picking up vendored generators.

October 15, 2009 | Unregistered CommenterMatt Jones

Yeah, I don't trust (or use) config.gems in its current state either. But I'm simply not convinced that "bundle all your dependencies into the app" is an advance, after watching the difficulties that strategy caused in .NET-land for a few years. Rails seems determined to reinvent a broken wheel here.

October 15, 2009 | Unregistered CommenterMike Gunderloy

PostPost a New Comment

Enter your information below to add a new comment.
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>