241–250 of 1001 posts
Developer focused tool becomes mainstream.
Suites come in to maximize profit, engagement, in-app usages.
Early adopters leave looking for new developer focused tool.
Can't wait until slack gets snapchatitized features so I can put a cool filter and sticker on the code block messages in #devs
I've been suffering from this one too so I'll share the most annoying part for me. I frequently have reasons to type out glob patterns generally in backticks. The interface for this is completely broken in the new WYSIWYG editor. Here's what happens when I try to type: `/ / `, things work normally up until the second " " at which point the "/" between them becomes gets bolded, which makes no sense, because you can't…
There's some delicious irony in those slashes getting swallowed by HN's markdown parser.
Yay if we get more formatted messages on slack, and not just from technical users that have learned markdown.
Nay if I have to struggle to get my messages to format the way I actually want them to format. Having the new WYSIWYG editor show me the wrong formatting while editing doesn't make the new experience any less painful.
Slack formatting UX is now different from GitHub. Having to deal with Confluence/Jira formatting was already terrible enough - I now have to figure out how to type the same things three different ways.
The exact same happened with the draft feature. The importance of habit forming UI is very well documented, going back at least as far as Jef Raskin's The Humane Interface and the draft feature completely breaks it -- if you as much as accidentally leave a character in there, you can't find the channel/DM at its normal place. Despite repeated calls to make it optional, nothing. Threads are also broken, has always bee…
I actually love that drafts are brought to the top; it keeps things from getting lost for me. I even sometimes will write one character as a reminder I need to finish. But still, I understand your frustration. That being said, search makes it really easy to solve this. I rarely do anything other than Cmd+K/Ctrl+K, and type a character or two. For me, it's become second nature, and I never find myself searching around…
Earlier quoted context omitted.
The infuriating thing is that these would be some of the easiest possible features to add a toggle for. There's nothing wrong with liking drafts that float to the top, or rich text editing, but when a significant portion of your users is extremely upset about a tiny UX behavior like this, even if they end up being a minority, there's no excuse to not add an opt-out.
The real problem is that companies seem to think that users hate toggles. It's extremely hard for me to understand how valid this might be since I have techy people around me most often, but even when I don't, I've never heard someone complain about excess toggles. Ever. Is this a thing people do? I hear orders of magnitude more complaints about lack of toggles.
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…
CIDER is also the Clojure Interactive Development Environment that Rocks if it matters https://github.com/clojure-emacs/cider It likely doesn't as they seem unlikely to be confused.
Riot's CIDER is pretty much an internal codename though, and it's not split out (yet) for anyone else to use. So hopefully it's not too bad a namespace clash.
Extremely dumb way to roll out something without an option to disable it, especially with the excuse "we are listening to your feedback". They literally are not listening to it.
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.
Sadly they aren't going to implement some of my most used features from slack in ripcord so I stopped using it. Was ready to pay a ton of money to the dev as well.
The funny thing is that I am sure most of the people who work at slack know it's terrible, but no one asks them. There is a small cohort of product managers who probably have a plausible-sounding reason to do it, and they need to do something to justify their jobs, so they alienate everybody else because no one stops them. I am, to put it lightly, familiar with this in other companies.