Live data from Hacker News

Slack’s new WYSIWYG input box is terrible

quuxplusone.github.io

611–620 of 1001 posts

Re: Slack’s new WYSIWYG input box is terrible

#612
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!

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.

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.

Re: Slack’s new WYSIWYG input box is terrible

#613
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!

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.

Just give me the option to disable this shitty input.

Re: Slack’s new WYSIWYG input box is terrible

#614

Earlier quoted context omitted.

Yeah, the very first time I used Confluence I was in shock of how developer's at one time could have thought this was a good or useful product for discussing/planning code changes. For ticketing software, I find Clubhouse to be much better than JIRA. Normal markdown that doesn't drive you insane. Much slicker all around.

Concerning Clubhouse.io, it looks great, is there a download version? I know “Cloud is the way to go”, but I work in Men’s Rights (DV abuses, etc) and it is usually something that cloud companies don’t want on their platform, so we’re constantly at risk of being revoked.

Phabricator's ticketing system is excellent, and it's fully open source. Probably the best open source project management tool out there.

It's also very easy to self-host.

Re: Slack’s new WYSIWYG input box is terrible

#615
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.

Thank you! I didn't know about Ripcord, and so far it is great. I am amazed how fast it is. I'm also depressed that this amazes me, as it basically does what mIRC did for me over a decade ago.

This is developed in QT by one person, and it looks pretty feature-complete to me. I really don't understand why a company the size of Slack invests all their development effort into such a subpar platform as Electron, when a native solution is clearly doable with very limited resources.

Re: Slack’s new WYSIWYG input box is terrible

#616
post #493

I want to encourage everyone who doesn't like the WYSIWYG input box to use `/feedback` directly from within Slack to let the folks over there know about it. I believe this is one of those occasions in which tons of user feedback is crucial to at least make that awful thing optional.

Just wrote in, Thanks for sharing your experience with our new formatting UI. I'm sorry to hear it's been a little disruptive so far. There isn't a way to revert to the old formatting method, I'm afraid. We don't currently have plans to make the new formatting configurable though we are carefully considering all our customers' feedback.

Got the same message. Let's see if "carefully considering all our customers' feedback" means "hey, lots of people are annoyed by this" or "ignoring all our customers' feedback".

Re: Slack’s new WYSIWYG input box is terrible

#618
Recently wrote about how surprisingly computationally intensive typing in it is (https://juretriglav.si/what-happens-when-you-type-a-single-l...), so it’s doubly surprising that it also doesn’t work as expected. But text editing on the web _is_ hard, and hard to get right on deploy 1, so I’m sure they’ll iron out the kinks soon.

Re: Slack’s new WYSIWYG input box is terrible

#619

Can someone please help me come up with a reason for Slack not making this update opt out for those of us who can maneuver a keyboard?

Maintenance overhead. It doesn't seem like it would be a huge change, but only they will know the real cost of supporting both.

Yeah I don't know. I mean it's a textbox input field. How much maintenance can there be?
Post reply on HN