What's wrong with WYSIWYG editors
I think the biggest reason why the web is not a mass medium for the masses is because, although CSS has become the backbone of web design, WYSIWYG editors fail to visualize the effects of stylesheets on a webpage. What’s the point of a “What You See Is What You Get” editor that doesn’t let you see all of what you get?
Who cares about big, bad WYSIWYG?
Here’s the problem: The “masses” don’t see things in code. Ultimately, that’s why WYSIWYG editing is important: it democratizes the web.
The masses feel victimized by every other mass medium: People talk about how TV and fashion magazines are out to make them feel fat; newspapers are out to make them feel paranoid; radio is out to force-feed them whatever music “the man” wants them to listen to. But on the web, anyone can have a voice – if they know how to create a web page.
(Mo)WYSIWYG
Why do they call it “What You See Is What You Get” when, in reality, you don’t see all of what you get? They might as well call it (Most of) What You See Is What You Get. The only people who really have control over the web are those who see things in code.
This is a problem, but it is not unsolvable. Dreamweaver does a great job visualizing things like table widths. If it did something similar with things like div classes and IDs, it would be a step in the right direction.
Open source community also MIA
The open source movement isn’t helping, either. Seamonkey doesn’t visualize a stylesheet’s effects on a web page. Although Seamonkey’s original codebase, Mozilla, has spawned two child projects, one (Nvu) is officially defunct, and the other (KompoZer) hasn’t seen a major release in over a year.
The other big names in open source web development software are QuantaPlus and BlueFish – neither of which are WYSIWYG.
Open source software – the most democratic force in computing – still hasn’t made a decent WYSIWYG web editor.
Anna Ullrich
Dan Hiester
Dan Hiester
Anna Ullrich
Dan Hiester