5 ms·

OK it's mad funny, but what's so hard about `alias bx 'bundle exec'` in your .(bash|zsh)rc file?

by alinajaf 15y ago

secoif 15y ago
You shouldn't need an alias in the first place. "Convention over configuration."
- erichocean 15y ago
  Correct. The problem isn't the difficulty, it's the education. In my own project (SproutCore), we've used Ruby-based buildtools since 2007, and there is unanimous support to move to Node, precisely because running a modern Ruby stack requires so much education. We want to spend time in our IRC channel on SproutCore itself, not Ruby and it's myriad problems (all of which have "fixes" that "aren't so hard"). We're also moving to Node because the performance of the Ruby tools sucks, despite three rewrites (one by a member of the Rails core team, so not Ruby n00bs). The Node tooling? It's so fast that we can literally rebuild the entire project from scratch every time we reload the app and still load everything into the browser in under a second. Oh, and it took about a day to write. :/ That, to me, is why Node is taking off. The "I can get shit done quickly" factor is very high, the resulting code runs very fast, and the community is large, energetic, and helpful. Plus, pretty much everyone has to use JavaScript today.
  - alinajaf 15y ago
    > precisely because running a modern Ruby stack requires so much education Education about what? Can you give some specifics here? I'm genuinely curious as my day-to-day ruby development is pretty smooth and I haven't been doing it very long.
secoif 15y ago
You shouldn't need an alias in the first place. "Convention over configuration."
pilif 15y ago
or if that's too much use --binstubs to use "bin/rake balls" or if you are really, utterly crazy, use --binstubs AND set $PATH to contain './bin' and then use "rake balls".
- drogus 15y ago
  You can also use rvm with gemsets and just not use bundle exec at all. I'm amazed how quickly people forget about the things that bundler tries to fix. If you don't have any conflicts across your gems, you can basically use bundler as "just install my gems".
  - regularfry 15y ago
    This broke for me with Rails 3.1 last I tried it. I had to use bundle exec to get it to work.
- Buzaga 15y ago
  whats the fuzz about bundle exec? that annoyed me for some time but it's sure gone for some time that I don't even remember it anymore..
- asifskalam 15y ago
  I use rbenv with rbenv-bundler which runs the bundled binstub from my current directory when I run the command.
telent 15y ago
I have that exact alias. But it still adds 3 seconds to the startup time of any command run under it Maybe my laptop is underpowered, but three seconds to do essentially nothing is still a long time
- xentronium 15y ago
  I solved this by having isolated gemset for every project. This way I can use rake without fear of having multiple conflicting gem versions.
  - telent 15y ago
    Bundler and rvm? "now you have two problems" :-)
- alinajaf 15y ago
  Just to satisfy my curiosity, have you upgraded to 1.9.3 yet?

OK it's mad funny, but what's so hard about `alias bx 'bundle exec'` in your .(bash|zsh)rc file?

secoif 15y ago

You shouldn't need an alias in the first place. "Convention over configuration."

erichocean 15y ago
Correct. The problem isn't the difficulty, it's the education. In my own project (SproutCore), we've used Ruby-based buildtools since 2007, and there is unanimous support to move to Node, precisely because running a modern Ruby stack requires so much education. We want to spend time in our IRC channel on SproutCore itself, not Ruby and it's myriad problems (all of which have "fixes" that "aren't so hard"). We're also moving to Node because the performance of the Ruby tools sucks, despite three rewrites (one by a member of the Rails core team, so not Ruby n00bs). The Node tooling? It's so fast that we can literally rebuild the entire project from scratch every time we reload the app and still load everything into the browser in under a second. Oh, and it took about a day to write. :/ That, to me, is why Node is taking off. The "I can get shit done quickly" factor is very high, the resulting code runs very fast, and the community is large, energetic, and helpful. Plus, pretty much everyone has to use JavaScript today.
- alinajaf 15y ago
  > precisely because running a modern Ruby stack requires so much education Education about what? Can you give some specifics here? I'm genuinely curious as my day-to-day ruby development is pretty smooth and I haven't been doing it very long.

secoif 15y ago

You shouldn't need an alias in the first place. "Convention over configuration."

pilif 15y ago

or if that's too much use --binstubs to use "bin/rake balls" or if you are really, utterly crazy, use --binstubs AND set $PATH to contain './bin' and then use "rake balls".

drogus 15y ago
You can also use rvm with gemsets and just not use bundle exec at all. I'm amazed how quickly people forget about the things that bundler tries to fix. If you don't have any conflicts across your gems, you can basically use bundler as "just install my gems".
- regularfry 15y ago
  This broke for me with Rails 3.1 last I tried it. I had to use bundle exec to get it to work.
Buzaga 15y ago
whats the fuzz about bundle exec? that annoyed me for some time but it's sure gone for some time that I don't even remember it anymore..
asifskalam 15y ago
I use rbenv with rbenv-bundler which runs the bundled binstub from my current directory when I run the command.

telent 15y ago

I have that exact alias. But it still adds 3 seconds to the startup time of any command run under it Maybe my laptop is underpowered, but three seconds to do essentially nothing is still a long time

xentronium 15y ago
I solved this by having isolated gemset for every project. This way I can use rake without fear of having multiple conflicting gem versions.
- telent 15y ago
  Bundler and rvm? "now you have two problems" :-)
alinajaf 15y ago
Just to satisfy my curiosity, have you upgraded to 1.9.3 yet?