Hacker News Reader

Comment by tiborsaas | Hacker News Reader

We are different. For me it's exactly the "oh you changed it, never mind, I'll use it a bit differently from now on" situation.

View on HN

Same here. I've already mostly adapted to the new editor. There's some annoyances, but I love not having to send to myself just to see what the message will look like and how Slack's version of Markdown will interpret my formatting.

I wouldn't have a problem with this _if_ this were configurable. Its not. This is two pretty good UI/UX screwups in a row by Slack (this, and threads)

Slack's good at engineering and development. They used to be good at UI/UX, but whoever over there in the text entry product design slot is having a case of the Jony Ives.

I bet the majority (like 95%+++) of users are like that. I'm technical and while I've only used it for 1 day so far I still sent multiple code blocks and used formatting as usual. Maybe I'll run into problems but so far it's very much a whatever situation IMO.

A “preview” button would have facilitated this. Or even better, let users edit in the preview input if they want or the regular editor, switching back and forth as desired.

Funny enough, I kind of like it better - the way that the enter key changed in and out of a ``` block would always screw me up and I'd end up sending messages before I wanted to, and then instead of bugging someone for 1 message I have to send 3 with the middle being "sorry, hit enter too soon".

There was already a setting for this with markdown:

>When typing code with ```, Enter should not send the message.

>With this checked use ShiftEnter to send.

So they didn't really provide anything new here, just changed the default behavior.

edit: formatting

Had no idea. Thanks!

Reply on news.ycombinator.com