Vim Sucks Even Better

ViSucks but VimSucksEvenBetter.

But seriously, let's break it down.

• There are CUA [CommonUserAccess?] editors like VisualStudio and ExCode which we all know suck but sometimes there's nothing else handy ...
• There's pretty nifty shit like TextMate - but you have to pay someone and it's only on one platform. Hands up all professional programmers who want to be restricted to work on only one platform?
• There's EmacsEditor. Now we could get into a HolyWar but we all know that goes nowhere. I'll even agree that emacs was easier to script than BillJoy's original ViEditor. But nowadays, what, you'd rather hack in LispLanguage than in RubyLanguage? Hell yes! Don't let the door hit you in the butt. It's okay, it's slow enough to easily dodge.
  • That raises the question: For those who might, myself included, wouldn't that mean the ViperSucksEvenBetterThanVim?
  • Um, NonSequitur?
  • What? Where? I'll kill every NonSequitur I see.
  • Let me try again. I don't see how that follows. Can you please explain your thinking on this?
  • If I would rather program in EmacsLisp than in RubyLanguage, and yet have a Vi-like editor, then I would want Viper, the Vi emulation mode for Emacs. ViperSucksEvenBetterThanVim. --JesseMillikan
• There's VimTextEditor. Beautiful, open, all the bells and whistles either already baked in or easy enough to bolt on. It benefits strongly from having little old ViEditor sitting inside it wheezing away so we OldFarts can feel at home. But even for newbies it just sucks the best, no question, no contest. It'll lift the polish from your toenails if you let it.

---

FebruaryZeroSeven

CategoryVi