Live data from Hacker News

Slack’s new WYSIWYG input box is terrible

quuxplusone.github.io

51–60 of 1001 posts

Re: Slack’s new WYSIWYG input box is terrible

#51

lol product managers are such a bane for tech companies. they have to keep shipping features which no ones wants but they have to show they came up with and are shipping something. i think tech companies should try and avoid product managers and designers for as long as possible.

This sounds like you've never had a good one. A good product manager can make a world of difference.

perhaps but its so easy for product managers to not get to the heart of what hackers do

Re: Slack’s new WYSIWYG input box is terrible

#52
post #38

I'm going to take the opposite of this argument, and for bonafides, I run the product team for a 1000+ person company. I'm going to assume that this thing was tested out the wazoo, both qualitatively and behind enough feature-flags and buckets to keep Optimizely in business for a year. So I have no doubt that this wasn't just a hunch on their part, but something that they meticulously tracked. If I'm wrong, definitel…

Don't know why you're getting down-voted, this is a logical and sensible conclusion, from a business perspective.

Re: Slack’s new WYSIWYG input box is terrible

#53
post #41

Earlier quoted context omitted.

Smells of bad UX/design process - some senior "wants" this particular solution, despite their users showing direct feedback that it doesn't work for their needs.

I'd push back on your last point; there's a zero-sum feedback process here that is invisible. You're seeing the negative feedback from a vocal set of minority power users; the positive feedback from people isn't going to be known or seen in anything other than usage metrics. You say "users": how many, what percentage, what cohort..you get the idea.

How do you tell the difference between unpopular features and ones that are mostly liked? In both cases, only "a vocal set of minority power users" would say anything.

Re: Slack’s new WYSIWYG input box is terrible

#54
I went ahead and tried to reproduce the article's observations.

> when you do `foo()` it foos the bar.

I typed this exact sequence of characters in the new editor and it formatted exactly as one would expect.

> when you do bar.`foo()` it foos the bar

I was indeed able to reproduce this, and worse: if you put the cursor after the f, delete it, and type f again, the new f will happen before the backticks. One can tell this is about to happen by observing the cursor; even though the cursor is over the little box, it's black (as in for normal text) instead of red/salmon/whatever-that-color-is (as in for code).

That said, one can work around this by selecting all the text to be backtick'd and clicking the button (or pressing Ctrl-Shift-C); annoying, but slightly less annoying than having to retype things.

Re: Slack’s new WYSIWYG input box is terrible

#55
I wish Enterprise software or anything where I have to pay money to use had strict contracts about changes and mandatory opt-ins. It's ridiculous that in this day and age, we have to be worried about some PM deciding for large swathes of users what's best for them. I just want my tools to be predictable and usable and not have to relearn every bit of quirk someone fancied.

Re: Slack’s new WYSIWYG input box is terrible

#56
post #38

I'm going to take the opposite of this argument, and for bonafides, I run the product team for a 1000+ person company. I'm going to assume that this thing was tested out the wazoo, both qualitatively and behind enough feature-flags and buckets to keep Optimizely in business for a year. So I have no doubt that this wasn't just a hunch on their part, but something that they meticulously tracked. If I'm wrong, definitel…

That's all fine to have it for people who don't know markdown, but damn we should be able to turn it off if we don't want it.

Re: Slack’s new WYSIWYG input box is terrible

#57
The specific example shown in the attached article works fine for me in Slack with the updated editor.

``` when you do `foo()` it foos the bar. ```

Looks fine for me? Only the `foo()` is highlighted, not the entire line as shown. Have they pushed out a fix for this already?

Re: Slack’s new WYSIWYG input box is terrible

#58

lol product managers are such a bane for tech companies. they have to keep shipping features which no ones wants but they have to show they came up with and are shipping something. i think tech companies should try and avoid product managers and designers for as long as possible.

This sounds like you've never had a good one. A good product manager can make a world of difference.

One of the reasons I got into DevOps was because I got tired of dealing with shitty product managers. I've experienced maybe 2 good ones, ever.

Re: Slack’s new WYSIWYG input box is terrible

#59

Reading their non-replies on Twitter feels like I'm reading something specifically designed to piss me off. Smarmy apologies, low empathy, cocksure of how correct their vision of a chat service should be. This one in particular[1]: > The goal is for workflows to evolve, but we realize change can be a bit of a pain. "Stupid peasant, we are only here to help you. Once you see the glorious vision we have you will thank…

> You can use Cmd/Ctrl + Z to undo the format rendering within the text box, if that helps?

This is the one that got me. Yeah thanks, I've been using text boxes since the 90s, I know how to undo.

Now we'll get to find out if _they_ know how to undo.

Re: Slack’s new WYSIWYG input box is terrible

#60
Hmm I am actually not experiencing either of these bugs. The backtick character works as I'd expect. I definitely prefer the pre-WYSIWYG interface that is currently loaded in my Electron client though! Markdown is the perfect level of abstraction for styling without getting in my way!
Post reply on HN