Symphony on an old school web editor

Published on:

And yet another web publishing system: Symphony, "The biggest thing to hit web publishing since the keyboard." A pretty bold statement for something that exposes its users to WYSIFUC! At first sight (I haven't tested it beyond the online demo) this isn't going to ease my authoring pain (plus I'm not buying the XSL argument, at least not without an excellent XML WYSIWYG editor that even my favorite pointy-haired manager could use without loosing his latin).

Really, WTF with old school text editors? Some people say I'm exaggerating when I say that HTML did drive us at least ten years backwards in terms of GUI, but we had WYSIWYG text editing with Mac Write 21 years ago. Why can't we have something decent in the browser today?

Let's continue this way and the next thing I'll know is that we'll be having our web pages "typed in HTML in India"...

P.S. There is one really funny bit in their requirements:

Why doesn't Symphony support Internet Explorer?

Internet Explorer is filled with security problems and is not standards compliant. By supporting standards compliant browsers only, we can allow some funky stuff like the use of pseudo elements and attribute selectors to minimise on unnecessary <div> and <span> tags to save on file-size and also concentrate on proper, semantic code. Internet Explorer also doesn't support PNGs, an open standard image format.