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…
Keep in mind that Ripcord only needs to implement support for whatever Slack has already decided to implement. They don't need to do the whole "iterative design" process (which Slack is doing for them), which is precisely the part where C++/Qt things tend to fare poorly.
Slack’s new WYSIWYG input box is terrible
751–760 of 1001 posts
Re: Slack’s new WYSIWYG input box is terrible
#752Re: Slack’s new WYSIWYG input box is terrible
#753Earlier quoted context omitted.
Was super skeptical about all those Jira replacement SaaS’s out there. But Clubhouse is actually pretty good. For people on the fence, give it a try.
I for one am still waiting for usable task management SaaS - one that doesn't limit me to "epic/project/task" split, but instead recognizes that the work is being decomposed recursively , and has dependencies. All I really want is a system that lets me arrange my tasks into a DAG. B is a subtask of A. C and D are subtasks or B. E is a subtask of D. F is a subtask of A, but depends on D being complete. It's simple and…
Was there something you didn’t like about them?
Re: Slack’s new WYSIWYG input box is terrible
#754Re: Slack’s new WYSIWYG input box is terrible
#755Earlier 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,…
Re: Slack’s new WYSIWYG input box is terrible
#756Re: Slack’s new WYSIWYG input box is terrible
#757Earlier quoted context omitted.
> 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…
I work in the UX team for a major online retailer in the UK. We spend a large part of our time testing and validating our designs with real customers - not much goes live without us being sure it's the right thing. If something doesn't work for people, even if we think it's great, then it's gone.
Re: Slack’s new WYSIWYG input box is terrible
#758What is currently driving me crazy about slack is that: 1) Slack constantly makes subtle changes the UX that always takes a bit of time to figure out, I don't want to read update notes to find out how a critical comms tool has changed eg. yesterday the mac chat became psuedo wysiwhg and it broke my muscle memory and stuff bounces around while I'm typing, eg2. Drafts: FU, I didn't ask for you to reorder my UI around s…
Ugh, I can't stand the menu reordering for drafts!
Re: Slack’s new WYSIWYG input box is terrible
#759This 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.
Re: Slack’s new WYSIWYG input box is terrible
#760Earlier quoted context omitted.
I could not reproduce the example issues from the blog post, but the dual asterices inside the back ticks still fail for me. The upside is that it's now possible to have bold passages in monospaced text. I missed that before.
Here's a gif of the second issue from the blog post, just reproduced on my client https://i.imgur.com/X8FZJhi.gif
The web client on Firefox works better, though: https://imgur.com/a/X53iIlm
Edit: On Chrome it's broken for me too....