Re:When a rewrite isn’t: rebuilding Slack on the desktop
by ex3ndr on Monday July 22, 2019 @03:32PM
(#20501478)
iTerm2 eats 150mb+. Any cocoa app use that much of memory. App Store is 500mb just after launch.
[ Parent
| on HN ]
Re:When a rewrite isn’t: rebuilding Slack on the desktop
by seandougall on Monday July 22, 2019 @04:04PM
(#20501792)
> Any cocoa app use that much of memory.
What gives you that idea? Lots of apps have cruft, but that's nothing to do with Cocoa.
A "Hello, world!" in Cocoa uses around 13 MB, and the application bundle weighs in at 79 kB. The fact that Electron uses a bare minimum of over 100 MB just to get an application running is a source of some understandable consternation.
Re:When a rewrite isn’t: rebuilding Slack on the desktop
by Klonoar on Monday July 22, 2019 @04:11PM
(#20501859)
His point is, actually, quite valid. By the time you stop and rebuild all the image caching/media pieces, you'll end up with a hefty amount of memory usage too - Telegram (not the Qt one, the Cocoa one) will regularly climb up to 200ish MB if I have a media-heavy chat going.
People have skewed ideas of what's doable in memory constraints in 2019 for the feature sets that customers tend to expect.
Re:When a rewrite isn’t: rebuilding Slack on the desktop
by candiodari on Monday July 22, 2019 @05:12PM
(#20502369)
You're comparing absolute minimum of slack with a very heavily used Telegram instance. This is, given the similarity of the apps, not fair.
Compare a "media-heavy" slack with that Telegram, or compare with Telegram minimum.
Re:When a rewrite isn’t: rebuilding Slack on the desktop
by Klonoar on Monday July 22, 2019 @10:13PM
(#20503914)
No, I'm comparing the baseline: Slack's feature set.
To support that, you'd need far more than a "Hello World" stack.