4 ms·
> Add in that realistically you need to use Webkit (or some HTML renderer), at which point... 100MB is pretty good. Why do you need an HTML renderer? Slack us
by zeveb 9y ago
> Add in that realistically you need to use Webkit (or some HTML renderer), at which point... 100MB is pretty good.
Why do you need an HTML renderer? Slack uses Markdown.
emacs-slack is pretty lightweight …
- verandaguy_alt 9y ago>Why do you need an HTML renderer? Because it's objectively easier to do cross-platform GUI development using a single, well-defined and portable API that someone else maintains. That that API is nowadays de-facto WebKit supporting a HTML/CSS/JS stack is a natural, but unfortunate choice, and it's got a much lower barrier of entry and much less maintenance overhead than, say, Gtk+ or Qt.
- Klonoar 9y agoSlack uses Markdown, yes, but supporting everything under the sun that Slack does (especially as they add new things) is just much easier inside a Webview. The job of programming isn't to reinvent the wheel everywhere, it's just to deliver a product that doesn't suck - with native code, you're implementing a native solution for each feature Slack has or adds. Slack's content is web content. You're really arguing that an insane amount of extra engineering time should be spent to conserve, at best, an extra 40-50MB of RAM... and this is disregarding how modern RAM works anyway.
- progval 9y ago> Slack's content is web content. That's the underlying issue. If the "protocol" uses HTML, all clients will need to embed a web view.
- ksherlock 9y agoAnd to think the first WWW browser just used Next's Text view.