<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>bartread</author><text>&amp;gt; This reminds me of Atlassian&amp;#x27;s god-awful WYSIWYG editor.&lt;p&gt;Oh my goodness: triggered.&lt;p&gt;I&amp;#x27;ve barred the use of Confluence at our company specifically because of this.&lt;p&gt;&amp;quot;But, but, we used it at blah company.&amp;quot;&lt;p&gt;&amp;quot;Yes, so did I at blahblah company, and it was unbelievably crappy and made me angry every time I had to edit a document: we&amp;#x27;re not using it.&amp;quot;&lt;p&gt;I &lt;i&gt;DO NOT&lt;/i&gt; want to have to use what amounts to an extremely buggy, capricious, and neutered version of Microsoft Word 6 to edit the contents of a web page.&lt;p&gt;I will become extremely displeased with you if you waste my time by trying to persuade me it&amp;#x27;s a good idea. It&amp;#x27;s not.</text><parent_chain><item><author>tbabb</author><text>This reminds me of Atlassian&amp;#x27;s god-awful WYSIWYG editor.&lt;p&gt;In both cases, I get that some users can&amp;#x27;t or don&amp;#x27;t like to use a machine grammar&amp;#x2F;markup, however simple. For some people markup &lt;i&gt;is&lt;/i&gt; bad UX. Give them a WYSIWYG; that&amp;#x27;s fine.&lt;p&gt;But don&amp;#x27;t &lt;i&gt;remove&lt;/i&gt; the markup editor if your WYSIWYG editor is anything but a &lt;i&gt;perfect&lt;/i&gt; one-two-one replacement for markup (and I have never seen one that satisfies that).&lt;p&gt;IIRC there was a time when Confluence axed their markup, and inevitably a table or a template would get completely screwed, and there was nothing you could do but recreate it. &lt;i&gt;TERRIBLE&lt;/i&gt; design.</text></item></parent_chain></comment><story><title>Slack’s new WYSIWYG input box is terrible</title><url>https://quuxplusone.github.io/blog/2019/11/20/slack-rich-text-box/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>Twirrim</author><text>&amp;gt; IIRC there was a time when Confluence axed their markup, and inevitably a table or a template would get completely screwed, and there was nothing you could do but recreate it. TERRIBLE design.&lt;p&gt;There was.  I was using Confluence at the time, and it broke a lot of things.  There was a wonderful filed bug at the time with a lot of angry people on it, where they promised to bring the old mechanism back as an option, and they never did.  That told me everything I needed to know about Atlassian.</text><parent_chain><item><author>tbabb</author><text>This reminds me of Atlassian&amp;#x27;s god-awful WYSIWYG editor.&lt;p&gt;In both cases, I get that some users can&amp;#x27;t or don&amp;#x27;t like to use a machine grammar&amp;#x2F;markup, however simple. For some people markup &lt;i&gt;is&lt;/i&gt; bad UX. Give them a WYSIWYG; that&amp;#x27;s fine.&lt;p&gt;But don&amp;#x27;t &lt;i&gt;remove&lt;/i&gt; the markup editor if your WYSIWYG editor is anything but a &lt;i&gt;perfect&lt;/i&gt; one-two-one replacement for markup (and I have never seen one that satisfies that).&lt;p&gt;IIRC there was a time when Confluence axed their markup, and inevitably a table or a template would get completely screwed, and there was nothing you could do but recreate it. &lt;i&gt;TERRIBLE&lt;/i&gt; design.</text></item></parent_chain></comment><story><title>Slack’s new WYSIWYG input box is terrible</title><url>https://quuxplusone.github.io/blog/2019/11/20/slack-rich-text-box/</url></story>