Slack's Desktop App Now Launches 33% Faster, Uses 50% Less Memory (venturebeat.com) 81
Slack today announced it's deploying an under-the-hood upgrade for its desktop app to boost performance for companies and teams using the app for workplace collaboration. From a report: The latest version of Slack for desktop and internet browsers is due out in the coming weeks and promises a 33% faster launch time, 10 times faster launch of VoIP calls, and roughly 50% less memory usage. The news comes a month after Slack became a public company, listed as WORK on the New York Stock Exchange. Slack product architect and lead of desktop client rewrite Johnny Rodgers said the upgrade takes advantage of changes to Slack's underlying technology, like modern JavaScript tools and techniques and the React UI framework.
Re: (Score:2)
Yeah, it's kind of a case of "Too little, too late" now. Now that Microsoft has bundled Teams into Office 365, they are stealing Slack's customer base wholesale.
Thanks! (Score:1)
Thanks Slashdot! I'm installing this wonderful new and improved app as we speak. Also relaxing with a nice refreshing Pepsi and delicious Dominos Pizza!
4 months ago. (Score:2)
Development Team: Can we release the new version of the code, it works much better.
Boss: Lets wait until after we go public. Just in case we need to fire your team, that we we don't have as much complex code to offshore.
Should have used Rust (Score:2)
it runs 69 times faster than C and it's webscale like Mongo DB
Slashvertisement (Score:3, Interesting)
Wow, this is quite revolutionary. Are we going to get slashdot stories when all software in existence gets a bit of an upgrade, or just Slack? In an attempt to actually be on-topic, the real question isn't what miracle Slack pulled off to reduce startup and memory usage, but why it was apparently so grossly inefficient in the first pace.
This is actually News for Nerds (Score:2)
Are we going to get slashdot stories when all software in existence gets a bit of an upgrade,
A) There are a large number of people that use Slack. Especially technical people.
B) Slack is legendary for bloated runtime and memory consumption, I'd say cutting half the memory use is more than a "slight upgrade" and really helps a lot of people out.
I wouldn't want to see news about every upgrade either but this one truly does fall well in the realm of a useful Slashdot story, I will be looking for this release
Re: (Score:2)
Re: (Score:2)
This reads like an add for the "Ginsu" knife:
33% faster launch time
. . . and more!
10 times faster launch of VoIP calls
. . . and more!
roughly 50% less memory usage
. . . and more!
. . . and if you order right now . . . we will include the Spiral Slicer . . . at no extra cost!
Re: (Score:2)
Re: (Score:2)
Slack's underlying technology, like modern JavaScript tools
Re: (Score:2)
A more interesting story would be how Slack plans to defend itself from Microsoft Teams, which is rapidly stealing their paid subscribers by bundling their product with their Office 365 subscription. Last I heard, Teams now has more paying customers than Slack does.
Re: (Score:2)
Are you kidding? This is the first case of a piece of software developed in the last 10 years that actually shows any semblance of concern for resource usage. It *is* news!
I want to know more... Did they hire a non-millenial and as a joke decide to humour his concerns about the code quality?
Thank IRIX and Solaris/FreeBSD Linuxites (Score:1)
Re: (Score:2)
Re: (Score:2)
it reads like a comment for the Dropbox article from today vs. the Slack discussion.
Re: (Score:2)
Re: (Score:2)
Oh my god (Score:1)
Oh my god, who the hell cares?
100% less memory (Score:2, Insightful)
Not installing it uses 100% less memory
Why should I care (Score:2)
Re: (Score:2)
The answer is yes. To both questions.
Causes some compact laptops to thrash (Score:2)
Does Slack crashes so many times that startup time is an issue?
Even if it doesn't, a relaunch after a crash is not the only way to see startup time. Logging out of your operating system user session and logging back in also incurs startup time. This affects users who dual-boot Windows (to use or maintain a Windows application) and X11/Linux (to use or maintain an X11/Linux application).
Does Slack use so much RAM that makes your machine use swap memory?
I personally haven't used Slack's desktop app. But Skype's desktop app used well over 300 MB of RAM last time I tried it, as did Discord's. Given that Slack has been built on the same fr
Re: (Score:2)
Slack uses about 1 GB of RAM. That's why I always open it in a chrome tab where it only uses about 250 MB.
Re: (Score:2)
Is there a good way to write once and publish on all four of Windows, macOS, X11/Linux, and your website without "writing desktop apps in javascript with a bundled single-use browser"?
Re: (Score:2)
Neither C nor C++ includes a GUI framework. This means a program must use that of the platform (whether directly or indirectly), and all five major desktop and mobile platforms have different, mutually incompatible GUI frameworks. If you were in charge of writing the client software, how would you recover the cost of developing and maintaining a client that calls each of Win32, Cocoa, X11, Cocoa Touch, and whatever Android calls its GUI framework? If Qt, have you used Qt before?
Re: (Score:3)
Yes, Slack looks like an ircII client from the 80s, with emoji and some enhancement, but even on a quad core i7-8565 with 16GB of RAM and a SSD, it takes way too much time to load, and can take up to 1GB of RAM, mind you, for a window that displays some text. It also crash sometimes.
Re:Why should I care (Score:4, Informative)
Wow. So I now only need 16GB to run two channels? (Score:5, Insightful)
It's hard to comprehend how we managed to run multiple chat streams at once on 8MB computers. What sorcery was that!?!
Things IRC didn't do 2 decades ago (Score:1)
These features have become expected among proprietary web chat platforms, such as Skype, Slack, and Discord, and I would be rawther surprised if the IRC infrastructure from two decades ago supported any of them.
A. Voice and video chat.
B. Automatic previews of linked HTML documents, including a title and picture, done server-side so that dozens of people in the same channel don't all hit the website at once.
C. Support for mixing all major writing systems, including contextual right-to-left systems (such as A
Re: Things IRC didn't do 2 decades ago (Score:2)
Re: (Score:2)
My point is that these features are why people aren't still using the more RAM-efficient software from two decades ago. Many users find these features compelling enough that once Slack became available, they switched from IRC to Slack in order to use them.
bloatware (Score:4, Insightful)
Note: Those are median values (Score:2)
Performance may vary somewhat from computer to computer.
On my computer, for instance, the Slack desktop app uses 100% less memory.
"Modern Technologies" (Score:2)
An no more 100% CPU? (Score:2)
For some reason my Slack goes into "I'll use 100% CPU for no reason and you have to quit me to work again" mode randomly after bringing my (Linux) laptop out of standby. Once it did it just because I disconnected the network, so I think it's a network-related bug. Somebody busy-loops on EOF or Broken Pipe in there.
Actual writeup from Slack itself (Score:4, Informative)
For those of you interested in a little more technical detail about their rewrite, here's a link to their engineering report about the upgrade:
https://slack.engineering/rebuilding-slack-on-the-desktop-308d6fe94ae4 [slack.engineering].
Re: (Score:2)
Wow, the article starts with a 19-year-old quote from Joel Spolsky about a few software redesigns that "failed."
Who quotes this?
Let's take a casual glance (Score:2)
Let's take a casual glance.
Still runs under %APPDATA% on Windows instead of %PROGRAMFILES%. The former is where ransomware runs from and can be blocked by security policy.
Now bundled using webpak [wikipedia.org] according to Slack and the manifest messages in the log file.
Code name is "The Final Countdown" and commit is 06572bf.
Getting better all the time.
So god damn boring (Score:2)