111–120 of 184 posts
I miss the days where people recognized that using using 20MB of RAM for a trivial task is obscene. (Great tool, much better than the awful official client, but 20MB is actually a lot of RAM.)
So we've gone from IRC which worked perfectly fine to a billion dollar business just to port that software back to the terminal, where we started out to begin with I don't understand this world any more
Oh c'mon. Slack absolutely destroys IRC in terms of usability. And that's what ends up counting in the end.
Earlier quoted context omitted.
I fail to see how those things should be part of the protocol. That's like complaining HTTP doesn't support tags for your bookmarks. It's so out of scope. Unless, of course, you are talking about a user-friendly service offering IRC access to those who do not want to set up their own clients. So, something like IRCCloud, which does exist, fyi.
Okay. So why isn't IRCCloud better than Slack?
Rocketchat has much more feature parity to slack tbh. Comparing slack to IRC isn’t really fair even though they do the same thing.
I have used irc and slack and slack’s ease of use is its asset. I used freenode in high school and college to teach myself scheme. The barrier to entry is not something that can be explained as just use IRC.
Earlier quoted context omitted.
How is this Slack's fault, again? Or is the argument that messaging systems should be hard to install so they aren't misused? Seriously, what even is this comment chain getting at? If you work somewhere where always-on is a hard requirement, it doesn't matter what messaging system is used. Any place that would fire you for muting notifications would just as easily fire you for turning off email notifications. In shor…
Probably because Slack makes it easier to establish an "always-on" culture.
So we've gone from IRC which worked perfectly fine to a billion dollar business just to port that software back to the terminal, where we started out to begin with I don't understand this world any more
Teach my CEO, Design Director, and EVP of Sales to use this terminal slack client and you’ll understand.
Now I want a mattermost version of this; the mattermost native client for linux is so terrible as to be nigh unusable (I need to restart it every 24-72 hours as it just hangs regularly).
Maybe https://github.com/42wim/matterircd can help you. It also supports slack (experimental)
I actually do use this, but it is missing a lot of useful features, some of which seem unimplementable in IRC
One example: the mattermost clients won't register a message as "read" until you switch to that view, so if e.g. I check messages on my phone, I will see unread messages, but IRC doesn't have a way of communicating this between client and server so matterircd seems to mark all messages as "read" with mattermost)
Earlier quoted context omitted.
Probably because Slack makes it easier to establish an "always-on" culture.
Literally any other instant messaging program would have the same effect if the culture is toxic enough to allow it. Slack is no different other than name recognition and size.
Slack is focused on business.
Earlier quoted context omitted.
I was gonna say there's no way slack uses that much, then I actually looked. 750+mb.... What in the world are they doing?
It's based on Electron[1] which has a reputation for being a bit of a resource hog. The upside is that it makes it really easy to create a cross-platform app. [1] https://electronjs.org/
Now I want a mattermost version of this; the mattermost native client for linux is so terrible as to be nigh unusable (I need to restart it every 24-72 hours as it just hangs regularly).