521–530 of 1001 posts
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!
As someone who never got into slack, and never found it appealing... How so?
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!
This reminds me of Atlassian's god-awful WYSIWYG editor. In both cases, I get that some users can't or don't like to use a machine grammar/markup, however simple. For some people markup is bad UX. Give them a WYSIWYG; that's fine. But don't remove the markup editor if your WYSIWYG editor is anything but a perfect one-two-one replacement for markup (and I have never seen one that satisfies that). IIRC there was a time…
Earlier quoted context omitted.
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.
Given that Microsoft Teams is literally an existential threat, they really want to listen to feedback internally!
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.
For the life of me, I cannot figure out how to create two adjacent but separate code blocks. ``` one ``` ``` two ``` I've tried and tried.
The trick seems to be to add a blank final line, otherwise, it will not include the last line you typed in a code block.
This reminds me of Atlassian's god-awful WYSIWYG editor. In both cases, I get that some users can't or don't like to use a machine grammar/markup, however simple. For some people markup is bad UX. Give them a WYSIWYG; that's fine. But don't remove the markup editor if your WYSIWYG editor is anything but a perfect one-two-one replacement for markup (and I have never seen one that satisfies that). IIRC there was a time…
Every Atlassian product used / still uses a different markdown format, infuriating
It's quite annoying.
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…
Of course, it's not unlikely that they weren't so much afraid as that they thought nothing would be done with it anyway.
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 feedback on board, disabling the new formatting tool isn't an option that we will be offering.
We are committed to doing what we can to improve the new experience for you, and will continue to make improvements to the new editor. If there are any specific examples of how these changes are impacting your daily work, please let me know. The more detail you can share about your experience, the better we can understand how to keep making it better.
Regards,
Lucas.
Anyone know how to reverse engineer Slack desktop client?
I'd love to know whose idea it was, though. Maybe next time you could try congratulating them on "clever self-disruption of a successful product" or something similar to draw them out into the open.
The journey from hacker-friendly comms tool to mainstream train wreck must be quite a story.
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 want to immediately stop using this software but have no choice As someone who never got into slack, and never found it appealing... How so?