Before you all get too angry about the scandalous lies about your favorite editor note that this is a Verity Stob column. If you're reading it for a sober, fair-minded review of the various tradeoffs involved in the very serious business of text editing, you're doing it wrong.
> It turns out that my brain was only fitted with 72 bytes of "finger
memory"; furthermore it turns out to be EPROM, not Flash. I need to wipe
out all the WordStar keystrokes from 1986 (Ctrl+Y to delete a line,
anyone?) before I can add any more, and I have lost the ultra-violet
wiping-out gadget (ask your dad) needed to achieve this.<p>If he'd taken a look at the Zeus editor he would have found all the features mention (except the multi-cursor thing) and by selecting the WordStar key mapping, he wouldn't even have to erase the EPROM in his fingers.<p>Jussi Jumppanen<p>Author: Zeus
I must say this isn't nearly as funny as much of the Verity Stob posts, but no problem.<p>Mostly I was amazed to see that the <i>same</i> horrible bug in Notepad++ that seriously bit me once (the text replacement buffer silently truncated... aargh!) is the one mentioned here.
I'm often taken a bit back by how bad text looks in screenshots of Windows whatever. I really wouldn't want to look at that all day. Just my preference...
I like Sublime, but I think it's criminal that it can't show line endings. That's right up there with syntax highlighting in my list of must-have features. How often do line endings screw you? Since I tend to work on a lot of cross platform stuff, for me, it's all the time. I pretty much keep Notepad++ around just so I can pop things into it to look at their line endings.
<i>"Another giveaway [of Sublime's Mac influences]: Sublime comes with a set of colour schemes with names like Dawn, Expresso Libre, Monokai, Slush & Poppies and the Smell of Napalm in the Morning (I may have made one of those up).<p>Contrast this with an equivalent list from a Windows product (in fact Delphi VCL skins): Carbon, Charcoal Dark Slate, Emerald Light Slate, Golden Graphite, Slate Classico and Dark Beige Slate Classico Carbon (I may have made one of those up)."</i><p>To me, the second list comes off as more Mac themed. <i>Carbon</i> is a set of Mac APIs, <i>Charcoal</i> was the system font for Mac OS 8, and <i>Graphite</i> was the nickname of the Power Mac G4.<p>As for the first list, OS X has a desktop picture of poppies and Expresso[sic] could be Java inspired (like Cocoa, Gianduia, Espresso, Chocolat, Cappuccino, etc.) I doubt Apple would call anything 'Libre' in their English branding or documentation.
Well. At least he was pretty clear this was all his opinion.<p>But that's a couple of minutes of my life I'd like to get back.<p>I'm soOOooo glad I learned ed as my first editor which lead to a 30 year love affair with vi. Both of those editors sound painful to use.
"No support for Object Pascal ... minus 1 million points"<p>"How can I possibly use this as an IDE for theregister.co.uk backend systems when it doesn't support <i>object pascal</i>"<p>Get off my lawn! What smells like Mustard? The president is a demi-crat!
I will say TexPad is an amazing editor (as long as you don't need to do any unicode). Like verity I've been using it for many many years, and I have yet to find a replacement that I enjoy as much.<p>When I switched to Linux, I tried to learn all kinds of emacs and vi, and never enjoyed them as much. LightTable seems like it will finally answer my prayers, however.
For an article that prefaces it's dialogue with a desire to "leave the right-thinking reader with an impression of calm, reasoned rationality", it reads like opinionated tosh. How the author arrived at these six criteria as a reasonable litmus test for the applicability and usefulness of a text editor absolutely boggles the mind.
Sublime Text 3 fixes most of the problems mentioned in the article. It starts up fast, handles large files better. Still no option to show newline characters.
What an opinionated piece of crap TFA is. This kind of stuff is precisely why I stopped reading The Reg a long time ago.<p>Seriously:<p><i>"4. The editor should contain no implementation of Lisp."</i><p>Why do they do that? Because of course Emacs totally rocks in their last example, where you need to apply the same modification to various lines (in Emacs you'd probably use a macro repeating some search and replace using a quick Lisp substitution).<p>How do you even want to talk with people who argue for their own limitation?<p>Appeal to authority: I urge people to read <i>"Beating the average"</i> from pg.