News for hackers. Stuff that matters.

A comment on When a rewrite isn’t: rebuilding Slack on the desktop.

Re:When a rewrite isn’t: rebuilding Slack on the desktop by zeusly on Monday July 22, 2019 @12:38PM (#20499707)
I wonder if they increased their efforts after seeing VS Code (also a complex Electron app) run fast and memory-efficient.

Before VS Code everyone just accepted Electron's memory bloat, maybe slack even had plans to go fully native b/c no one thought it could be done properly.

[ Parent | on HN ]
Re:When a rewrite isn’t: rebuilding Slack on the desktop by doc_gunthrop on Monday July 22, 2019 @03:07PM (#20501234)
> memory-efficient.

Not how I'd describe a text editor that consumes 700MB+ of RAM at any given time.

[ Parent | on HN ]
Re:When a rewrite isn’t: rebuilding Slack on the desktop by spookthesunset on Monday July 22, 2019 @05:08PM (#20502343)
Yes, because vs code is just a mere text editor.
[ Parent | on HN ]
Re:When a rewrite isn’t: rebuilding Slack on the desktop by wgoodall01 on Monday July 22, 2019 @09:30PM (#20503753)
Replace "text editor" with "IDE," and that 700mb figure doesn't seem so extravagant.
[ Parent | on HN ]
Re:When a rewrite isn’t: rebuilding Slack on the desktop by flukus on Monday July 22, 2019 @10:37PM (#20504008)
It does to those of use that remember upgrading to (I think) 128MB of RAM to run Visual C++ 6, it's not like a heap of new features have been added since.
[ Parent | on HN ]