Live data from Hacker News

Slack’s new WYSIWYG input box is terrible

quuxplusone.github.io

671–680 of 1001 posts

Re: Slack’s new WYSIWYG input box is terrible

#671

Earlier quoted context omitted.

While I understand why this change can be annoying to the tech savvy folks of hackernews, it can be quite helpful for those who aren't that tech savvy and want easy ways to bold, italicize texts (that make up majority of the slack user base). Heck I am sure most of the slack users wouldn't even know it was possible to bold, italicize on slack using markdown.

Why does anyone (tech savvy or otherwise) need to bold or italicize anything. In my mind bolding/italicizing are nice-to-haves alongside emoji. You wouldn't compromise the entire functional user experience of the central feature of your app for nicer emojis. (at least I hope not).

You literally just italicized "need", and I read it the way you intended it.

That's why tech people italicize stuff.

Re: Slack’s new WYSIWYG input box is terrible

#673
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, caprici…

Just to let you know, if you haven’t used it in a whole, Confluence (Cloud) has a completely new editor that seems decent, it just rolled out a few weeks/months ago.

Re: Slack’s new WYSIWYG input box is terrible

#674
post #528

I have contacted them, and they replied me with this Lucas (Slack) Nov 20, 9:15 PM PST Hi there, Thank you for taking the time to write in and provide this feedback. I apologize for the disruption to your existing workflows. Our aim is to build an editor that works for all Slack users to better format their messages and clearly communicate in channels, regardless of their technical expertise. While we are taking all…

You should point out how blatantly contradictory these two sentences are...

Our aim is to build an editor that works for all Slack users

disabling the new formatting tool isn't an option that we will be offering

...unless their goal is to reduce "all Slack users" to "only those who don't need the option"...

Re: Slack’s new WYSIWYG input box is terrible

#675

This is funny because I work across the street of Slack’s office in Vancouver, Canada and two Slack engineers who I frequently chat with during our daily commute already told me they —and a handful of other employees— hate the WYSIWYG input box too, but were afraid to express their feelings because their role is irrelevant compared to the people who made the decision to ship it.

It's genuinely hard to make a good design for something, but if you put the time and effort required, that's the difference between Atom and VS Code.

The only way I know how to make a good design, is to have a good Product Owner. Prototyping helps a little bit, User testing absolutely not. You can have five different PO working on the same epic and still get a bad design, but it only takes one to find the perfect solution.

That input box story is not different. They could have made the WYSIWYG feature compatible with the "old" input method by changing the visual without altering the character flow (eg: The brown fox). Apparently, no one thought of that...

Re: Slack’s new WYSIWYG input box is terrible

#676
post #495

This is not one of those "oh, that's annoying, i'll have to remember that and learn to work around it" issues. It's more like "I want to immediately stop using this software but have no choice". Its driving me crazy - Slack is all text input. Don't break text input dummy!

Exactly. Personally, I recommend switching to Ripcord as a Slack client. That's what I did some time ago, and I couldn't be happier.

I seem to remember reports of people having their accounts suspended for using third-party clients (though I may be thinking of Discord accounts). Either way, I've used ripcord a bit and though it's not much to look at, it certainly gets the job done. I'm personally grateful for an alternative.

Re: Slack’s new WYSIWYG input box is terrible

#677
post #456

Earlier quoted context omitted.

It's in their ultimate best interest to find a new vocation. You can't just hit undo or tab out of this one.

That's for them to decide, not for HN users to prescribe. Internet commenters underestimate the impact their personal comments have on the targeted person by at least 10x. It's just not nice. It's unlikely that the person in question is reading this HN thread, but there's a chance that they are, and that means we should do better.

Being a lead at a company as high profile as Slack carries a lot of weight career wise. These people can take it and probably thrive off of it.

Re: Slack’s new WYSIWYG input box is terrible

#678

What is currently driving me crazy about slack is that: 1) Slack constantly makes subtle changes the UX that always takes a bit of time to figure out, I don't want to read update notes to find out how a critical comms tool has changed eg. yesterday the mac chat became psuedo wysiwhg and it broke my muscle memory and stuff bounces around while I'm typing, eg2. Drafts: FU, I didn't ask for you to reorder my UI around s…

Ugh, I can't stand the menu reordering for drafts!

Re: Slack’s new WYSIWYG input box is terrible

#680
post #495

This is not one of those "oh, that's annoying, i'll have to remember that and learn to work around it" issues. It's more like "I want to immediately stop using this software but have no choice". Its driving me crazy - Slack is all text input. Don't break text input dummy!

On the topic of the old, am I the only one who found the switched behaviour of enter/shift-enter inside/outside a ``` block somewhat annoying?

This you can actually fix - check out Settings -> Advanced -> Input Options for enter behaviour in code blocks.
Post reply on HN