Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Slack’s new WYSIWYG input box is terrible

quuxplusone.github.io

Post reply on HN
Print view View original

331–340 of 1001 posts

Re: Slack’s new WYSIWYG input box is terrible

#331

Post by farisjarrah »

nicwolff wrote: post #320
imglorp wrote: post #299

Earlier quoted context omitted.

Preach it. It seems every text input box across the product line has a different input method: BB, Jira, and Confluence. You'd think they might standardize with one to be less user hostile.

Jira still has two different WYSIWYG implementations on different pages. On the "classic" issue form, you still enter `{code}this is code{code}`, but if you open that issue in the sidebar of the backlog page, it's Markdown.

Oh man, this issue is particularly insidious for my work flow. Like... Why the hell isn't it consistent even across pages within the same project?!?

Re: Slack’s new WYSIWYG input box is terrible

#332

Post by journalctl »

nwallin wrote: post #235
Swizec wrote: post #157

Earlier quoted context omitted.

> Only in the software industry would someone tell me that my professional tools should change because change is inherently good Translation: "we're paying all these engineers and product managers and they need something to do"

The crazy thing to me is that if they rolled out a native desktop app that was maybe a little bit lacking in features and used ~20MB RAM and had this particular misfeature in it and called it beta, people would applaud them for it, especially here on HN. Instead they spent actual time, effort, and money making their product worse. My company has certain deficiencies, but one of our core principals is that we'll never…

After this change I really want to develop a native chat application on Windows and OS X. I think it’s almost to the point where someone who did they could make a killing.

Re: Slack’s new WYSIWYG input box is terrible

#334

Post by erklik »

rdhatt wrote: post #48

You can submit feedback to Slack using "/feedback" command. The nice thing it appears they have real people give you real replies. I encourage people to use it. I asked them for the option to turn it off. An excerpt from their response. > ... we understand that this has caused a disruption in workflows for some of our more technical users. While we don't have any active plans to make this configurable at the moment,…

God, That reply is a million times better than the pseudo-helpful condescending crap they were spouting on twitter.

Re: Slack’s new WYSIWYG input box is terrible

#335

Post by thelittleone »

rbavocadotree wrote: post #314
p1necone wrote: post #306

Earlier quoted context omitted.

Agreed, isn't slack only popular because of "cool" tech startups picking it up initially?

65 of the fortune 100 companies use slack.

I’m always a little wary about these claims. For example I worked at a Fortune 500 before and I created a setup on an app like Slack using my corporate email account.

There is a big difference between “used by company Y” and “used by tiny team X inside company Y” (probably without IT approval).

Re: Slack’s new WYSIWYG input box is terrible

#336

Post by ryankshaw »

Tade0 wrote: post #45

As someone who used to be part of a team developing one of the most popular in-browser WYSIWYG editors: 1. Browser WYSIWYGs are really hard to make. 2. All browser WYSIWYGs are terrible. Avoid rolling your own WYSIWYG if you can. Even if you have a team of 1500 people at your disposal.

what would you say are the top few out there now? looking to adopt an editor for a large website

Re: Slack’s new WYSIWYG input box is terrible

#337

Post by netghost »

rdhatt wrote: post #48

You can submit feedback to Slack using "/feedback" command. The nice thing it appears they have real people give you real replies. I encourage people to use it. I asked them for the option to turn it off. An excerpt from their response. > ... we understand that this has caused a disruption in workflows for some of our more technical users. While we don't have any active plans to make this configurable at the moment,…

Just remember, the people who read and respond to you are probably not the people who either implemented or designed features and bugs you may run across.

Re: Slack’s new WYSIWYG input box is terrible

#338

Post by bhl »

Tade0 wrote: post #45

As someone who used to be part of a team developing one of the most popular in-browser WYSIWYG editors: 1. Browser WYSIWYGs are really hard to make. 2. All browser WYSIWYGs are terrible. Avoid rolling your own WYSIWYG if you can. Even if you have a team of 1500 people at your disposal.

How do you feel about ProseMirror, and what browser WYSIWYG editor did you work on if you don't mind? I'm using it right now to build a personal notes editor, but there isn't much open source components to model my custom nodes to.

Re: Slack’s new WYSIWYG input box is terrible

#339

Post by bartread »

tbabb wrote: post #111

This reminds me of Atlassian's god-awful WYSIWYG editor. In both cases, I get that some users can't or don't like to use a machine grammar/markup, however simple. For some people markup is bad UX. Give them a WYSIWYG; that's fine. But don't remove the markup editor if your WYSIWYG editor is anything but a perfect one-two-one replacement for markup (and I have never seen one that satisfies that). IIRC there was a time…

> This reminds me of Atlassian's god-awful WYSIWYG editor.

Oh my goodness: triggered.

I've barred the use of Confluence at our company specifically because of this.

"But, but, we used it at blah company."

"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're not using it."

I DO NOT 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.

I will become extremely displeased with you if you waste my time by trying to persuade me it's a good idea. It's not.

Post reply on HN