201–210 of 225 posts
Still waiting for an option to disable "drafts" (channels all of a sudden jumping to the top of the channel list)
Your mistake is showing a channel list. Hide unread channels; it's the only way to use Slack IMO.
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.
A Tesla Model S is fundamentally the same product with the same value add as a Ford Model T. Sure, the Tesla may be faster or more efficient or whatever now, but what it is at heart is the exact same thing as the Ford was 111 years ago.
* test1
* test2Earlier 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++...
People complain about Ruby being dead, or don't talk about it at all because it's not relevant anymore.
Earlier quoted context omitted.
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 ?
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.
Earlier quoted context omitted.
If I'm in non-bold mode and I click in the middle of a bold word/sentence to make edits, do I automatically start typing in non-bold? That sounds much more annoying than helpful.
> If I'm in non-bold mode and I click in the middle of a bold word/sentence to make edits, do I automatically start typing in non-bold Yes! You'd need to press ⌘B to enter bold mode, and then begin typing. It's ever-so-slightly more effort, to be sure. But, I loose so much more time trying to add non-bold to the end of a bold section, or vise versa. I can learn to use systems which behave in repeatable and understand…
Text color, background color, strikethrough, superscript, etc.? If I'm typing in a block of red text, is my new text black unless I tell it again to be red? If I'm editing a superscript, do I type normal text in the middle of it and then need to select it and make it superscript afterward? Editing text that was highlighted with a yellow background?
It might be an easy toggle for bold/italic/underline but there's a lot of other text formatting that would either need to behave differently or would become a huge pain. Personally I'd rather keep it consistent.
Earlier quoted context omitted.
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…
This is how I imagined threads working when they were announced, but it seems they are never used consistently. How exactly do you manage to enforce that rule? Even if this worked, it's just a nice step toward a full comment tree (like HN or reddit). I get the impression some people find that format confusing, but I think it's vastly superior. I assume programmers generally prefer it.
Earlier quoted context omitted.
Not sure Chromium is to blame here. All the WYSIWYGs in all the environments I've ever seen I found fiddly and unpleasant to use.
Really? It works fine in Edge (edgehtml-based version) and FireFox.