Slack outage: Degraded performance and connectivity issues

Re:Slack outage: Degraded performance and connectivity issues by maccard on Friday October 16, 2020 @05:41PM (#24805323)

I'm on a 2017 MacBook Pro right now with a 300Mb connection, and using the web interface takes multiple seconds to change channels, has a > 1 second delay in typing (resulting in missing keystrokes). My workstation isn't a particularly pleasant experience and it's _much_ beefier than this machine. My partner uses MS teams on a beater of a windows laptop with at most 4GB of ram and it performs substantially better.

I've made multiple support complaints to slack about their memory usage, there's been times where it's been using Gigabytes of memory on my workstation, and I've actually had to kill slack to compile on more than one occasion.

[ Parent | on HN ]

Re:Slack outage: Degraded performance and connectivity issues by jakear on Friday October 16, 2020 @05:54PM (#24805425)

> My partner uses MS teams on a beater of a windows laptop with at most 4GB of ram and it performs substantially better.

So not an electron issue, an engineering issue. That's I think at the root of all these "electron is bad" comments... poorly engineered code is slow. It will be slow if it's C++ or JS or Perl. But well engineered code is fast. And it can be fast in C++ or JS or Perl.

[ Parent | on HN ]

Re:Slack outage: Degraded performance and connectivity issues by maccard on Friday October 16, 2020 @07:24PM (#24805975)

I don't disagree, but starting in electron is going to make your life much more difficult. Well engineered electron-based code may still be slower than shoddy C++

As an example, I've been playing with web frameworks recently. Asp.net running on dotnet core is roughly 10 times faster than node running express. While well engineered js might not get much slower, you'll never close that gap.

[ Parent | on HN ]