Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Slack’s new WYSIWYG input box is terrible

quuxplusone.github.io

Post reply on HN
Print view View original

711–720 of 1001 posts

Re: Slack’s new WYSIWYG input box is terrible

#711

Post by darkwater »

pgcosta wrote: post #707

What a bunch of whining babies. Are you really this upset with such a tiny change? :D I like the new editor. They shouldn't revert the changes. Like any change on any software, people will complain first, some issues will be solved, and then will adapt and stop complaining. How can this have such an impact in your lives? Stop slacking and work ;)

I've just received the update this morning, I "complained" for a moment but to be honest it's not that bad neither the end of any world. Plus, I can't really reproduce (or maybe understand?) the Markdown problem he's reporting about "when you do `foo()` it foos the bar". It work as previously did and as the author expects on my computer.

Re: Slack’s new WYSIWYG input box is terrible

#712

Post by cmiles74 »

acdha wrote: post #656
Nextgrid wrote: post #637

Earlier quoted context omitted.

Why does everything need to cater to idiots instead of making them learn? If we continue down this trend we’ll end up with keyboards with a single button to cater to some monkeys out there who can’t manage to use a proper keyboard, at the expense of everyone else’s productivity. Is this the future we really want?

Because they’re not idiots but rather people with different priorities and backgrounds who were underserved previously. You might disagree that this is helpful but it’s unlikely that you know more about Slack’s users than their UX team. Treating everyone involved with respect is a much better strategy than what you’re doing.

I suspect Slack is aiming for the customers they would like to have in the future at the expense of the customers they actually have right now.

Re: Slack’s new WYSIWYG input box is terrible

#714

Post by Iv »

sambe wrote: post #495

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!

Uh... you just have to press the right arrow to get out of the code block when you type. Seriously, that's not even one more key press, that's just pressing "right" instead of `

Re: Slack’s new WYSIWYG input box is terrible

#716

Post by UI_at_80x24 »

e12e wrote: post #574
TeMPOraL wrote: post #503

Earlier quoted context omitted.

Exactly. Personally, I recommend switching to Ripcord as a Slack client. That's what I did some time ago, and I couldn't be happier.

There's also wee-slack: https://github.com/wee-slack/wee-slack

Just switched over to this. Thanks for posting.

Re: Slack’s new WYSIWYG input box is terrible

#717

Post by HarveyKandola »

benhurmarcel wrote: post #450
kelseydh wrote: post #355

Earlier quoted context omitted.

100% agree that Clubhouse > JIRA. If I hear a company uses JIRA, I will actually question whether I want to work there.

Can you recommend a replacement for Jira that can be self-hosted? Many companies cannot store their data on a third-party server.

Take a look at Gemini[0] for self-hosted issue management and help desk ticketing.

[0] https://www.countersoft.com

Re: Slack’s new WYSIWYG input box is terrible

#718

Post by phyzome »

livueta wrote: post #50

Specific bug gripes aside: I see this editor as emblematic of Slack's broader shift away from what I think it should be (primarily synchronous chat; irc with a friendlier ui and integrated bouncer features) towards what many people seem to want to use it as (async-heavy pseudo-replacement for email where I get to sit and watch the "...is typing" indicator flicker while somebody writes an essay at me). My rule of thum…

« My rule of thumb generally is: if I need significant rich text formatting in a message I'm writing, it should probably just be an email. »

Italic and bold I can do without. But code blocks are absolutely necessary for my day job, especially during a production incident. (Email won't cut it for that!)

Re: Slack’s new WYSIWYG input box is terrible

#719

Post by asdf21 »

TazeTSchnitzel wrote: post #573
greggman2 wrote: post #474

Earlier 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…

The reason the Windows 95 interface was so much better than what came before it was because Microsoft did loads of user testing and changed their design heavily based on it.

And imo it's still basically the best design.

98 and XP were basically just flavors of win95 and those were everyone's favorite, UI wise.

Re: Slack’s new WYSIWYG input box is terrible

#720

Post by AnIdiotOnTheNet »

CloudNetworking wrote: post #710
SubuSS wrote: post #700

Earlier quoted context omitted.

We shouldn't fetishize control as much. In >15 years what I have seen is that OSS comes with a huge cost of attention - that you'd be better off focusing on your business need. Running most of these OSS even at a medium employee count scale is a full-team-commit-nightmare. It essentially means your it department now needs a specialist who will be able to handle your org quirks, remember the tweaks and keep baby sitti…

We don't need OSS in this case, we need open protocols so anyone can use any other client, proprietary or not.

We've had a perfectly good open chat protocol since... gosh, I don't even know. It's called IRC and it's so simple you can implement a server or client in python in under an hour.

This is what happens when you over-engineer things.

Post reply on HN