Live data from Hacker News

Slack’s new WYSIWYG input box is terrible

quuxplusone.github.io

701–710 of 1001 posts

Re: Slack’s new WYSIWYG input box is terrible

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

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 with my team for consideration in the future."

Re: Slack’s new WYSIWYG input box is terrible

#702

It's fascinating to see how tools turn into environment people wanna live in. Its a god damn tool, dont commit your lives to it. Use it, abuse it, it doesnt work - toss it.

"Toss it" is not an option when it is a product your company uses.

Annoyances like this is not enough to make me toss it but it is still an annoyance that could have been fixed by giving user an option

Re: Slack’s new WYSIWYG input box is terrible

#703

Earlier quoted context omitted.

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 n…

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. Several things I can think of: "quantity is not quality"; JS developers far outnumber everyone; making web apps look exactly the way they want is easy, and they are not interested in platform-native functionality,…

Ehhh for Skype it's mostly a Skype thing. Pretty much every decision made about Skype be it platform, features, ... Is wrong. I'm convinced Skype within Microsoft is now some middle step they put their product managers through for a year or two without paying much attention to them, and each tries to implement his "own mark" on it as some sort of achievement. The alternatives to that theory are too scary.

Re: Slack’s new WYSIWYG input box is terrible

#704
post #117

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.

Bad sign. If the rank and file are afraid to give honest internal feedback, they have a management problem. At least for me, that's a time-to-leave signal.

It's a company with non-unique tech run by salespeople, of course they have a management problem.

Re: Slack’s new WYSIWYG input box is terrible

#706

In their defence (not the defence of the WYSIWYG box itself) - they quite likely have done lots of user testing that has shown clear desirability, improved value to user, improved usability, etc etc. You have to remember Slack's target persona is probably no longer the Engineer (If it ever was) - it's more likely a much less tech-savvy employee who finds WYSIWYG editors very handy to create rich text inputs. I guess…

> they quite likely have done lots of user testing that has shown clear desirability, improved value to user, improved usability I have never worked at a company that did user testing or if they did it was always done in a way or interpreted in a way to back up the designer's opinion. I don't think I've once in my entire 40 yr career seen a designer test with users, find out something was bad, and change their design…

Reminds me when Jetbrains designers decided that colored icons were distracting to developers.

They never backed up their claim with any data, and instead released a very partial plugin to shut up dissent.

Basically all they do is look at Adobe UIs and copy them, even if IDEs and Photoshop are not used by the same people and not for the same usage ...

Re: Slack’s new WYSIWYG input box is terrible

#707
What a bunch of whining babies. Are you really this upset with such a tiny change? :D

I like the new editor. They shouldn't revert the changes. Like any change on any software, people will complain first, some issues will be solved, and then will adapt and stop complaining.

How can this have such an impact in your lives?

Stop slacking and work ;)

Re: Slack’s new WYSIWYG input box is terrible

#708
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…

I mailed them too, and got a human response instantly. They're good at that.

Re: Slack’s new WYSIWYG input box is terrible

#709

In their defence (not the defence of the WYSIWYG box itself) - they quite likely have done lots of user testing that has shown clear desirability, improved value to user, improved usability, etc etc. You have to remember Slack's target persona is probably no longer the Engineer (If it ever was) - it's more likely a much less tech-savvy employee who finds WYSIWYG editors very handy to create rich text inputs. I guess…

> they quite likely have done lots of user testing that has shown clear desirability, improved value to user, improved usability I have never worked at a company that did user testing or if they did it was always done in a way or interpreted in a way to back up the designer's opinion. I don't think I've once in my entire 40 yr career seen a designer test with users, find out something was bad, and change their design…

[deleted]

Re: Slack’s new WYSIWYG input box is terrible

#710
post #700

Earlier quoted context omitted.

This is another argument against using proprietary SaaS solutions for such crucial purposes as business communication. There are free open source alternatives which give you full control and privacy: Mattermost, Riot.im, Rocket.chat, Let's Chat.

We shouldn't fetishize control as much. In >15 years what I have seen is that OSS comes with a huge cost of attention - that you'd be better off focusing on your business need. Running most of these OSS even at a medium employee count scale is a full-team-commit-nightmare. It essentially means your it department now needs a specialist who will be able to handle your org quirks, remember the tweaks and keep baby sitti…

We don't need OSS in this case, we need open protocols so anyone can use any other client, proprietary or not.
Post reply on HN