Terrible decision to make this a part of core

  • This is not why I chose WP 12+ years ago. I chose it because it was clean code. Design & content should remain separate. This is no better then all the other crap out there. Now content is full of code on export. No more clean content.

    This makes me sad. ??

    • This topic was modified 5 years, 11 months ago by WebWeaver64. Reason: tags
Viewing 1 replies (of 1 total)

  • I basically said this in reply to someone else just a moment ago. +1

    They are trying to structure input using markup specs intended for output. The result? All of the worst problems of the unusable WYSIWYG failures.

    Markup languages are to enable producers to mark up an undifferentiated stream of input to make it easy to structure repetitive output while lowering overhead on input. Only that. Input = mark up. Output = structure.

    When you get that order confused or reversed, you make life a million times harder for everyone. People use WordPress precisely to build with HTML/CSS/JS/PHP. They don’t use WordPress in hopes of avoiding HTML/CSS/JS/PHP. There are other platforms and products for that, and they are far less capable. (For a reason!)

Viewing 1 replies (of 1 total)
  • The topic ‘Terrible decision to make this a part of core’ is closed to new replies.