91–100 of 1001 posts
What I don't like about it is that it takes too much vertical space for the row of icons at the bottom. What I do like about it is that I'm forever pasting code snippets ``` code .. ``` and it saves me the time of entering the 3 backticks.
Based on the title, I was dreading checking this out but... I kind of like it; Keyboard accelerators for dropping in and out of the various block and list modes, quick action for code etc.
What I don't like about it is that it takes too much vertical space for the row of icons at the bottom. What I do like about it is that I'm forever pasting code snippets ``` code .. ``` and it saves me the time of entering the 3 backticks.
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.
At the risk of sounding like a shill, I'd like to shill Zulip. We started using it instead of Slack, and it has been amazing . It's fast, everything is designed to help you get to conversations quickly, keyboard accessibility is second to none and the streams is a much better default than rooms. I can't recommend it enough, it's well worth the money even though they have a nice free tier and are OSS so you can self-h…
> there is no way to go back to plain old Markdown input Can’t you just tap on the “Aa” icon to hide it?
This hides the row with the buttons, but the behavior of textinput remains the same
The new behavior is maddening.
Reading 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…
On the web site they put it this way "Slack is the collaboration hub that brings the right people, information, and tools together to get work done."
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.
Pah. Next you'll tell us that once Ripcord shows you some messages, its "N new messages in this chat" notification actually goes away. Now that would be a killer feature, if Slack managed to implement it.
Amusingly, for https://riot.im we just shelved our WYSIWYG editor efforts after trying two completely separate implementations over the years (one via Draft.js, the other via Slate.js) because: a) it's a nightmare to get right, b) nobody used it anyway (it was optional), c) chat isn't a wordprocessor, d) markdown (commonmark) + floating formatting toolbar is good enough. Our current editor was written from scratch (c…
You know what else has a terrible WYSIWYG editor? Microsoft Teams. It's kind of sort of like Markdown, except when it isn't, or when it breaks. At least it's a step up from Lync.
Amusingly, for https://riot.im we just shelved our WYSIWYG editor efforts after trying two completely separate implementations over the years (one via Draft.js, the other via Slate.js) because: a) it's a nightmare to get right, b) nobody used it anyway (it was optional), c) chat isn't a wordprocessor, d) markdown (commonmark) + floating formatting toolbar is good enough. Our current editor was written from scratch (c…
You know what else has a terrible WYSIWYG editor? Microsoft Teams. It's kind of sort of like Markdown, except when it isn't, or when it breaks. At least it's a step up from Lync.
It is infuriatingly terrible. A regression. So many times I've had similar woes with the code block and quote block mechanisms too. Another truly bizarre feature I noted and sent a bug report about was that when adding an image to an "Action" the _minimum_ size requirement is 512px by 512px. For an image that is never rendered larger than 64x64.
> never rendered larger than 64x64
On a high-density display, that 64px x 64px image covers a lot more surface area than 64x64 actual pixels on the physical display. I suspect that this 512x512px requirement is related to scaling factors on devices with high DPI displays.