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

The latest version of Slack has a setting to disable the WYSIWYG editor

twitter.com

Post reply on HN
Print view View original

181–190 of 225 posts

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#181

Post by tiborsaas »

72deluxe wrote: post #179
fortytw2 wrote: post #18

It's pretty incredible to think that for all the billions of dollars around Slack it's still fundamentally the same product with the same value add that it was when it first launched. Sure, maybe it's faster or more efficient or whatever now, but what it is at heart is the _exact_ same thing it was on Day 1.

And still just a web browser underneath! If they used a native toolkit this bug wouldn't exist, no?

Probably not, but then you would have 100 different bugs browses handle flawlessly nowadays.

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#182

Post by tiborsaas »

swader999 wrote: post #112
zamalek wrote: post #95

Earlier quoted context omitted.

The reason is that content editable is a gaping hole in the HTML5 spec, at least last time I checked, there are tons of undefined undefined behaviors (not a typo) where vendors have to choose what they want to do and where developers have no idea that the behavior does not exist in a specification. My very wise coworker made every effort to avoid that minefield. I thought he was wrong for many years, but I have been…

I always thought the entire cms space, the idea that non coders could manage web content, was a non starter just because of the editors.

But it's utterly inefficient to use coder time to manage web content. That's why the best idea is to create a block by block content editor with textareas or severally limited editors that remove and reformat HTML that's being generated. I've seen good results thanks to this.

I agree though, whenever I included a full WYSIWYG editor to a CMS the end users created unimaginable havoc. "Hey it's Word, I know this".

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#183

Post by tomashubelbauer »

coryfklein wrote: post #57
saltcured wrote: post #40

Earlier quoted context omitted.

Ha, I wish I could disable "threads" so nobody else can use them...

We have a culturally enforced strict rule of moving literally ALL new conversations into a subthread and I absolutely LOVE it. This means that if you want to respond to a comment, you never do it in the channel but in the subthread of _that_ comment. This means that when you browse the channel itself, each individual line represents a conversation on a specific topic. You can essentially browse the "headlines" of the…

Isn't this just Microsoft Teams? Not to be a shill (I prefer Teams over Slack but don't love either). In Teams the editor box in each channel creates a new post on which people then comment. Is Slack, a channel is just another group chat. What you do turns Slack into Teams in this regard seems to me. Which as far as I'm concerned is a better system, I just wish Slack had tools to enforce it stricter ways than as a cultural rule.

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#184

Post by beshrkayali »

ArmandGrillet wrote: post #6

Dark mode, better performances, option to disable divisive new features: Slack might be making it harder to focus at work but the product itself improved quite a lot in 2019, kudos to the PMs.

Incompetence deserves no praise when the mistake gets fixed.

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#185

Post by Semaphor »

vorticalbox wrote: post #160
jammaloo wrote: post #35

Earlier quoted context omitted.

The above demo works fine in Firefox, FWIW. I had a large hand in building a WYSIWYG email editor a few years back, using direct DOM editing, that was the most full featured available at the time. I would only recommend it to people with very high pain tolerance, as the differences between browsers are stark, undocumented and hard to work around.

It doesn't work fine on Firefox android.

Same for FF preview.

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#186

Post by gsich »

o-__-o wrote: post #102
paxys wrote: post #65

Earlier quoted context omitted.

Where did IRC go?

Away after botnets (and later dogecoin) figured out its a free decentralized comms platform and caused every major enterprise to block all IRC ports out of fear of being owned. At least this was my experience in the early 2000s, which is why I gave up on IRC circa 2006-ish. The death kneel was the lack of a google/apple cloud-backed IRC app, so any mobile use of IRC was pretty much a death wish for your battery (this…

>The death kneel was the lack of a google/apple cloud-backed IRC app, so any mobile use of IRC was pretty much a death wish for your battery (this may have changed but meh damage has already been done).

Not really. Google/Apple also have a connection (or more) open to their servers, but IRC would kill the battery? It's the usage, not that the connection is open.

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#187

Post by reportgunner »

gota wrote: post #7
ArmandGrillet wrote: post #6

Dark mode, better performances, option to disable divisive new features: Slack might be making it harder to focus at work but the product itself improved quite a lot in 2019, kudos to the PMs.

Side comment: I've tried to use Slack's dark mode but had to quit. I was constantly having to download images to be able to read the black-over-transparent background of matplotlib images (that's apparently the default for the axis, markings, legends, etc.) It's not a matter of changing my code, too, because I want to see the images posted by _other_ people

Honest question: what is the added value of having transparent background on matplotlib images ?

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#188

Post by reportgunner »

gempir wrote: post #158
asmint3 wrote: post #121

Don’t understand the need for a WYSIWYG editor in the first place. It’s not a word processor. The need to add formatting to a Slack message should be rare enough that the WYSIWYG overhead just isn’t worth it.

They want to make the product appeal to all users and not just techy ones. And If I product managers or CEO or whoever can print his message bold he's happy. Very few non techy people know what markdown even is. (From my own experience asking friends etc.)

I'm sorry, but what users ?

AFAIK Facebook, Instagram, Snapchat, Twitter doesn't have a WYSIWYG editor.

Are there some hidden users that send font size 30 all capitals red colored text in Times New Roman to each other ?

Re: The latest version of Slack has a setting to disable the WYSIWYG editor

#189

Post by ProZsolt »

mehrdadn wrote: post #138
Someone1234 wrote: post #51

Earlier quoted context omitted.

“There are only two kinds of languages: the ones people complain about and the ones nobody uses.” -- Bjarne Stroustrup I've found this quote extremely true, but not just with programming language but with all things. People complain about Slack because they use Slack a lot, so minor quibbles become a daily frustration. It is when people go quiet about a product that you should really worry. They're either extremely h…

> “There are only two kinds of languages: the ones people complain about and the ones nobody uses.” -- Bjarne Stroustrup > I've found this quote extremely true My impression of Python, Ruby, etc. hasn't been that they're in either of those categories, though I'll grant you that they don't compete in the same space as C++...

I use Ruby(not Rails) daily. I love the language. It's really good for fast prototyping or small scrips but I can complain all-day long for how bad is to maintain big codebases because of the dynamic nature of it. I really miss type hints that can make this much easier.
Post reply on HN