I have contacted them, and they replied me with this Lucas (Slack) Nov 20, 9:15 PM PST Hi there, Thank you for taking the time to write in and provide this feedback. I apologize for the disruption to your existing workflows. Our aim is to build an editor that works for all Slack users to better format their messages and clearly communicate in channels, regardless of their technical expertise. While we are taking all…
Slack’s new WYSIWYG input box is terrible
721–730 of 1001 posts
Re: Slack’s new WYSIWYG input box is terrible
#722Earlier quoted context omitted.
Same here. I'd made some nice (and quite simple) tooling to parse docstrings out of a Python project and turn them into Markdown that I could copy-and-paste into Confluence. It was so convenient to run something like "make documents" to basically compile the project's documentation from inspecting the project itself! But then Confluence broke their editor by making it WYSIWYG-only. And in response, I broke Confluence…
What is something else? I’m interested, if it’s available for download (not cloud).
Open source core supporting WYSIWYG, Markdown, Code and more.
Re: Slack’s new WYSIWYG input box is terrible
#723Earlier 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…
Re: Slack’s new WYSIWYG input box is terrible
#724Earlier 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…
> as it basically does what mIRC did for me over a decade ago When Atlassian finally pulled Hipchat last year I was tasked with finding the replacement. Turns out the one that met everybody's needs best was a local IRCd and whatever desktop client for it people liked. Some problems have been solved correctly for a while; chat is one of them.
It is very far from a solution in 2019.
Re: Slack’s new WYSIWYG input box is terrible
#725Re: Slack’s new WYSIWYG input box is terrible
#726Earlier quoted context omitted.
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.
Re: Slack’s new WYSIWYG input box is terrible
#727Earlier 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…
I mailed them too, and got a human response instantly. They're good at that.
Re: Slack’s new WYSIWYG input box is terrible
#728Earlier quoted context omitted.
Why does everything need to cater to idiots instead of making them learn? If we continue down this trend we’ll end up with keyboards with a single button to cater to some monkeys out there who can’t manage to use a proper keyboard, at the expense of everyone else’s productivity. Is this the future we really want?
Because they’re not idiots but rather people with different priorities and backgrounds who were underserved previously. You might disagree that this is helpful but it’s unlikely that you know more about Slack’s users than their UX team. Treating everyone involved with respect is a much better strategy than what you’re doing.
Re: Slack’s new WYSIWYG input box is terrible
#729Earlier quoted context omitted.
Given that Microsoft Teams is literally an existential threat, they really want to listen to feedback internally!
Microsoft Teams is pretty horrible
Re: Slack’s new WYSIWYG input box is terrible
#730Earlier 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…