Earlier quoted context omitted.
They actually just fixed that in 4.0: https://slackhq.com/introducing-a-more-efficient-slack-deskt... I'm currently sitting at 400MB total usage (including helpers) for 4 workspaces.
400MB? Not bad for a chat client that sends a few bytes of text.
Slack was down
191–200 of 243 posts
Re: Slack was down
#192Earlier quoted context omitted.
My favorite are the conspiracy theories as to why the outages are seemingly so close together in this Summer of 2019. All kinds of imaginative reasons abound. My best guess is summer vacation :) it's at least true for my company who was one of the featured outages
My best guess is that "sequencing creates narratives." It's like in baseball, how a player who hits .333 over the season will have 0-10 and 10-10 stretches where he either can't hit everything or demolishes every pitch he sees. You'll often see sports news come up with stories for why this is happening, and most of the time it's just "this is how statistics work". TL;dr- complex systems are complex, and trying to und…
Re: Slack was down
#193If you're a community driven project or organization using Slack, then take a look at https://zulipchat.com/ for something that sucks less, and is open source software. I've found it much more pleasant to use and less buggy than Slack.
Re: Slack was down
#194Earlier quoted context omitted.
Such is the nature of slightly optimized Electron apps, T-Mobile Digits Desktop app is a similar resource hog. Using the browser based version often is less resource intensive.
Tried that, they actively employ darkpatterns to coerce users onto desktop apps. I even asked them to stop asking for an app install on their links that you open from inside the webapp and they told me to get stuffed and use the desktop app.
Re: Slack was down
#195Earlier quoted context omitted.
They actually just fixed that in 4.0: https://slackhq.com/introducing-a-more-efficient-slack-deskt... I'm currently sitting at 400MB total usage (including helpers) for 4 workspaces.
How is CPU and I/O use on the newest version?
Re: Slack was down
#196Re: Slack was down
#197Earlier quoted context omitted.
I can honestly say that I have never checked or cared about how much RAM Slack uses. Or any other software for that matter. It's certainly not an issue that I'd use as the basis for deciding which team communication tool to use.
Yeah see the people that are caring about this are caring because it has used up all of their available RAM, has pushed stuff into Virtual Memory, and it is causing performance problems for their system. Or, if they are IT, it is causing performance problems on their users' systems. This is a pretty reasonable complaint when you're talking about a system with 2gb, and a chat application that uses 1.5gb of memory...or…
Re: Slack was down
#198P.S I don't work for slack or have any affiliation.
Re: Slack was down
#199Earlier quoted context omitted.
It seems that you could take any old-school internet tech, add some flashy GUI, slap "for enterprise" label and you get a great and popular solution that solves the problem noone ever could solve. Maybe it's time for gopher for enterprise
Lots of old technology is really good but has a bad user interface. There is something to be said for packaging up something in a nice, good looking, easy to use way. I mean, look at how many companies use Sumologic and hosted ElasticSearch for log ingestion. Theoretically speaking, with grep, regex and python you could make all the graphs and charts yourself, there is no real reason to purchase these (pretty expensi…
Pretty tangential, but I observed that exact phenomenon recently after looking at the recent VR headsets: Oculus Rift and HTC Vive existed for at least a few years. Tried them, was pretty fun, but tangling with wires, having to have a powerful PC on hand, that 1-2min set up every time before you want to use it, it was all killing the usability for me.
Then Oculus Quest comes out earlier this year. Pretty much similar tech (a few differences, no need for PC, but can be used with one through easy sideloading), but no wires and no need for a PC connection. Every time I want to use it, I don't need to fiddle with my PC. I put the headset on, it wakes up in a few seconds at the exact spot I left it last time. I put it down, it goes to sleep in 15 seconds.
I ended up spending an hour or two almost every day for the past two months playing with it, as opposed to the previous headsets (most of which were left on the shelf a few weeks after the initial purchase). The only major advantage that Quest has over previous gen is easy and frictionless UX.
It got to the point where every single friend of mine who tried it at my place ended up purchasing their own headset the day after. And those people were some of the biggest VR skeptics, after their experiences with original Vive and Rift.