I'm just getting into Ruby and converting to vim as my primary editor, and I didn't even know that this is a "hip" thing to do. All of a sudden I feel trashy fo

I'm just getting into Ruby and converting to vim as my primary editor, and I didn't even know that this is a "hip" thing to do. All of a sudden I feel trashy for making logical choices. I think the author misjudged why people like me choose Ruby and vim -- choices that have nothing to do with each other, btw. I'm a fan of terseness and readability. Ruby has a reputation for both. I've never heard the following phrases spoken: "Perl is great for writing DSL's." "Perl is very readable." The most amazing experience has been going on GitHub on day one, reading the Rails, Haml, Sinatra, Tilt, you name it, code and being able to understand virtually any part of it. This is not only a testament to the language, but also a testament to the quality of the frameworks and the API's that are being produced with it. Show me a web framework written in Perl that I can dig into and understand with zero Perl experience. Vim, on the other hand, is a sour-sweet topic. Here is the only reason I'm using vim: everything else sucks ___. Vim also sucks ____ because in 2011 it is still a text editor that can't copy paste using the "normal people" shortcuts. I'm looking forward to the day I finally customize vim enough to match Notepad in usability. As much as vim usability sucks, I know that I can spend a year customizing it (and it will take a year) and be able to rely on it for the rest of my life. In contrast, there is no such incentive to invest into the monstrosities riding over the JVM (not calling names). Also, screencasts are great because I read all day and its tiring, physically tiring. Sitting back, relaxing my eyes and being educated while I sip on a coffee and have a cookie is my idea of fun. Screencasts are free, bite sized, training. By the author's logic Khan Academy is worthless as an educational tool because most of it is written somewhere.