3 ms·
Oh, absolutely - but don't confuse a Rails problem with a Ruby problem. It wasn't Rails causing problems, it was Ruby itself.
by ajacksified 15y ago
Oh, absolutely - but don't confuse a Rails problem with a Ruby problem. It wasn't Rails causing problems, it was Ruby itself.
- ericd 15y agoIf I'm getting set up, I really don't distinguish between Rails itself being irritating and one of its dependencies being a PITA. Those dependencies are part of the architecture of Rails, so it gets the blame. It's not like I need foo version of ruby if I'm just doing some quick scripting.