A couple of our zipline guides in the truck. http://instagram.com/p/bC3Gg4Mnng/
-
#Dream: They made a video about it. There was Benny Hill music, crying, bridges and bad acting. I drew a comic about it. 2/2
#Dream: @bleything was @topfunky's partner in @peepcode. Geoff was going to London for two weeks leaving Ben in charge. 1/2
This is not just the Texas government.
Or the U.S. government.The problem is government.
Revolutions have happened for less. Heads have literally rolled. #fightback
Just posted a video http://instagram.com/p/bAspM2snuf/
Moth in a lantern. http://instagram.com/p/bApAoWMnqw/
In reply to:@indirect Oh well. I'll just move on with my life.
@indirect Like run rake tasks that shouldn't matter what Ruby I'm using. Like `rake db:migrate`, etc.
In reply to:@indirect It's not that.
I get the need to test in dev on the same Ruby as prod.
What's frustrating is that I can't do other things...
In reply to:@indirect Oh well, I guess.
In reply to:@indirect Good one. :P
In reply to:@indirect I think it reaches too far.
In reply to:@indirect Sure. But I can't `rake -T`, for example, while using a Ruby different from the one in my Gemfile.
In reply to:@indirect My app runs great on rbx-19 or MRI-1.9, for example. I don't want to force developers to install one or the other to work on it.