For... a second?

For... a second?

Posted Oct 4, 2007 21:48 UTC (Thu) by Los__D (guest, #15263)
In reply to: For... a second? by nix
Parent article: The Mono Project: You Might Expect the Unexpected (Linux Journal)

Compared to, well, typing. The editor stutters every time it pops up an autocomplete window, and that window is always right over where I was planning to type next, or over some code I'm consulting.
No stutter here. And again, you can TURN IT OFF, if it bothers you. If you like the IntelliSense idea (Why give it a new name? Oh well, it IS MS after all), it is more than a bit of help, and frankly, still the best of the editors that supports it, luckily, Eclipse is getting closer and closer. If you get easily distracted, I guess a list showing is a problem.

No can do. It's much too inflexible.
That's another matter, hardly anything is comparable to Emacs' flexibility in any circumstance.

It's grossly underequipped with shortcuts compared to Eclipse, vi, *and* Emacs, and it's not configurable enough.
I'm not the big "configure the hell out of anything I touch" type, I'm usually flexible myself. I don't really miss any shortcuts, but then we are different.

But of course because I gave up and switched back to my preferred editor (which has admittedly got the benefit of familiarity) I imagine you'll ignore everything I have to say as well.
No, you actually had reasons, the OP, and the topic starter just threw bull.

---

to post comments