I've given up entirely on the Slack desktop app and use Ripcord exclusively. Much faster, more responsive and easier to use for 99% of my time spent on slack.
How is voice chat on Slack working in Ripcord? I'm guessing not at all?
Slack’s new WYSIWYG input box is terrible
11–20 of 1001 posts
Re: Slack’s new WYSIWYG input box is terrible
#12Their stock has been decimated. Tempted to still short it at this price. Very clear it’s not much more than a feature that has quickly been commoditized.
Re: Slack’s new WYSIWYG input box is terrible
#13Oddly, I don't see those issues with Firefox.
If I type an inline `foo()` it converts to WYSIWG as soon as I type the closing back-tic and everything I type after is back in normal text mode. If I left-arrow to have the cursor inside the formatted div but before "f" and type "bar." I wind up with the expected effect `bar.foo()`.
It takes one extra arrow press to move the cursor beyond the invisible back-tic to shift from the inline code to plain text regions before or after the block.
I preferred the old input just because I don't like having content jump around while typing. I'd still rather hit the preview tab to see it rearrange itself.
Re: Slack’s new WYSIWYG input box is terrible
#14we are all talking about this at work. this is the worst forced update!
Re: Slack’s new WYSIWYG input box is terrible
#15> I think the only way to insert text at the beginning of a code span in the WYSIWYG editor is to highlight the first character of the span and type over it
This seems better than what I was doing: put the cursor after the first character, type the new beginning, add the same character and remove the same character from the beginning. Thanks for the tip!
Re: Slack’s new WYSIWYG input box is terrible
#16It is pretty astonishing how much Slack was able to grow from their initial 2 years of being ahead of the curve in UX, despite being mediocre/bad on every other front since.
Re: Slack’s new WYSIWYG input box is terrible
#17Oddly, I don't see those issues with Firefox. If I type an inline `foo()` it converts to WYSIWG as soon as I type the closing back-tic and everything I type after is back in normal text mode. If I left-arrow to have the cursor inside the formatted div but before "f" and type "bar." I wind up with the expected effect `bar.foo()`. It takes one extra arrow press to move the cursor beyond the invisible back-tic to shift…
I use Firefox and I've had nothing but trouble from the text box. It's just atrocious, I don't know why they'd do this when the previous box worked so well. At least make it an option!
Re: Slack’s new WYSIWYG input box is terrible
#18I get that it's bad right now, but it hasn't even rolled out fully. It's quite clearly not 100% done or it would be 100% rolled out.
This seems like literally one bug.
Re: Slack’s new WYSIWYG input box is terrible
#19Reading their non-replies on Twitter feels like I'm reading something specifically designed to piss me off. Smarmy apologies, low empathy, cocksure of how correct their vision of a chat service should be.
This one in particular[1]:
> The goal is for workflows to evolve, but we realize change can be a bit of a pain.
"Stupid peasant, we are only here to help you. Once you see the glorious vision we have you will thank us."
[1]: https://twitter.com/slackhq/status/1192147475672510474?s=21
Re: Slack’s new WYSIWYG input box is terrible
#20I've given up entirely on the Slack desktop app and use Ripcord exclusively. Much faster, more responsive and easier to use for 99% of my time spent on slack.
The speed difference between Ripcord and Slack is just night and day. I had forgotten applications can respond faster than I can type, yet here we are.