Rails in particular is the worst about that. Bonus points if you're working on an older codebase that's been upgraded through a couple versions, but is still fa

Rails in particular is the worst about that. Bonus points if you're working on an older codebase that's been upgraded through a couple versions, but is still fairly out of date. I hate having to keep so much fiddly crap in my head when, with a better language and/or framework, my tools could tell me what I need to know when I need to know it. Ugh, dynamically-named automagical variables and methods the definitions of which are ungoogleable and ungreppable. Gross. "Magic" is almost never worth the cost. A Sinatra project written with some discipline and taste isn't too bad, though, and Ruby's still my preferred language for throw-away one-off tiny scripts, mostly because it's very concise, has lots of available libraries, and isn't Javascript.