Live data from Hacker News

Slack’s new WYSIWYG input box is terrible

quuxplusone.github.io

801–810 of 1001 posts

Re: Slack’s new WYSIWYG input box is terrible

#801
Did Slack ship a buggier version of this yesterday? I have it on one of my workspaces, and it's fine.

I can still type `backticks` in the editor, with the exact same combinations of keystrokes I used before, it's just that they render as they will on the channel, rather than showing me the backticks (and only when I type the closing backtick. GIF here: https://i.imgur.com/o3wPWN0.gif)

Triple backtick does the same, and I can easily type another triple backtick to exit the code block, same as before. It's literally identical ergonomics to the previous editor, except it's showing me the formatting I can expect.

I have to think that maybe they issued some hotfixes to the wysiwyg editor in the past 24 hours to some workspaces? Or people are just way too up in arms about something that has literally no impact other than maybe some wasted screen real estate showing formatting buttons...

Re: Slack’s new WYSIWYG input box is terrible

#803
post #701

Earlier quoted context omitted.

I’ve already put my money where my mouth is and sent an email saying I intend to cancel all future payments to Slack unless they give the option to disable it, I suggest everyone else does the same.

I expressed my discontent to them as well and just received this reply: "I'm afraid there is no way to disable this at the moment, and it's not in the roadmap to roll back on this feature. That said, we're still in the initial stages here, so our focus right now is listening to feedback as we consider certain changes for improvement as we move forward. You've raised some fair points here, so I've shared your feedback…

> and it's not in the roadmap to roll back on this feature

How can anyone remain a customer of such idiots?

Re: Slack’s new WYSIWYG input box is terrible

#804
post #659

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.

Wasn't the target audience of Slack, at least initially, tech-savvy IT teams? If they take away plain text and markdown -- or make them harder to use -- they are alienating their early adopters. Not sure what their user base looks like now, though.

I've seen it used in some surprising places. Last time I had my contact prescription checked, the staff used Slack to communicate between the doctor/assistants in room and the front desk.

Re: Slack’s new WYSIWYG input box is terrible

#807

Did Slack ship a buggier version of this yesterday? I have it on one of my workspaces, and it's fine . I can still type `backticks` in the editor, with the exact same combinations of keystrokes I used before, it's just that they render as they will on the channel, rather than showing me the backticks (and only when I type the closing backtick. GIF here: https://i.imgur.com/o3wPWN0.gif ) Triple backtick does the same,…

Because it now more then a textarea, my mind automatically adapt and expect to give me a newline, but instead I am filling up channels with premature messages. Weird.

Re: Slack’s new WYSIWYG input box is terrible

#808
post #803
post #701

Earlier quoted context omitted.

I expressed my discontent to them as well and just received this reply: "I'm afraid there is no way to disable this at the moment, and it's not in the roadmap to roll back on this feature. That said, we're still in the initial stages here, so our focus right now is listening to feedback as we consider certain changes for improvement as we move forward. You've raised some fair points here, so I've shared your feedback…

> and it's not in the roadmap to roll back on this feature How can anyone remain a customer of such idiots?

[deleted]

Re: Slack’s new WYSIWYG input box is terrible

#809

Did Slack ship a buggier version of this yesterday? I have it on one of my workspaces, and it's fine . I can still type `backticks` in the editor, with the exact same combinations of keystrokes I used before, it's just that they render as they will on the channel, rather than showing me the backticks (and only when I type the closing backtick. GIF here: https://i.imgur.com/o3wPWN0.gif ) Triple backtick does the same,…

It may have been buggier yesterday, but I had the change applied to my desktop client today and it is still buggy. Try to edit an `inline code` section. Or enter two code blocks back to back. Or paste in anything with formatting, especially if there is a code block at the end.

Re: Slack’s new WYSIWYG input box is terrible

#810

Did Slack ship a buggier version of this yesterday? I have it on one of my workspaces, and it's fine . I can still type `backticks` in the editor, with the exact same combinations of keystrokes I used before, it's just that they render as they will on the channel, rather than showing me the backticks (and only when I type the closing backtick. GIF here: https://i.imgur.com/o3wPWN0.gif ) Triple backtick does the same,…

Many edge cases are different.

To name one: You realize after finishing your code block that the first two lines of it actually shouldn't have been part of the code block, but should have been normal text above.

Go ahead and try to make this change with the new system.

Compare that to what you would have done with the old, plain-text system.

Post reply on HN