Earlier quoted context omitted.
Yea a glorified chat app with video chat, audio chat, screen sharing and screen takeover remotely, file uploading, 3rd party integrations doing multiple things depending on your team setup, etc. I'd hardly call it a glorified chat app.
Messages.app does all of those and uses a tenth of the RAM.
Migrating Slack's Desktop App to BrowserView
61–70 of 214 posts
Re: Migrating Slack's Desktop App to BrowserView
#62Earlier quoted context omitted.
> Telegram, an app actually written in native code, is currently using ~500MB on my machine right now. I took a look at the Telegram source code right now, and…I'm not impressed. It appears to be written without a real knowledge of how Swift or Cocoa works, has no consistent style, and seems like it reinvents significant portions of standard APIs. Like anything, the benefits from migrating to "native" only work if yo…
Meh, there's often reasons to reinvent a portion of an API. You'd need to be more specific about what you see there that's an issue. I also pointed out Telegram because people, consistently, in every one of these threads, trot it out as an example of a native chat app (I don't count the Qt version in any of this, because it does not in any way feel native on macOS). To be honest, I welcome anyone to point out a compe…
Yes, but I don't feel that a message app really needs to do this to the extent that Telegram does–they've managed to make their app look out of place on macOS.
Re: Migrating Slack's Desktop App to BrowserView
#63Christ, so many buzzwords and frameworks and rewrites but all users ask for is a damn chat application with few tabs. Either I'm getting old and grumpy, or it used to be possible in the year 2000 without your computer fans taking off and 1gb of ram.
In year 2000 you might only have to care about Win98. And that’s it. In 2017 there’s no tech stack that lets you write consistent UIs across multiple platforms. Except, unsurprisingly, Electron
Re: Migrating Slack's Desktop App to BrowserView
#64What the hell is taking up all that RAM? Slack is using over 800MB of RAM on my computer right now, and it's completely idle. I've got a C# process on my computer right now handling thousands of messages per second and consuming 1/20th the RAM. If you rebuild Slack in Xamarin you'd probably drop your RAM consumption to under 50MB, just a guess. JS fiends are gonna tell me C# ain't JS, and I agree. TypeScript ain't JS…
Re: Migrating Slack's Desktop App to BrowserView
#65Earlier quoted context omitted.
Yea a glorified chat app with video chat, audio chat, screen sharing and screen takeover remotely, file uploading, 3rd party integrations doing multiple things depending on your team setup, etc. I'd hardly call it a glorified chat app.
Messages.app does all of those and uses a tenth of the RAM.
Re: Migrating Slack's Desktop App to BrowserView
#66Earlier quoted context omitted.
When these kinds of things come up there's often complaint that desktop apps running in the browser are inefficient. As it happens, I agree. An old favourite of mine, Adium, probably never used 600 MB because I'm pretty sure my PowerBook G4 had less RAM than that. But I think it's a mistake to jump to the conclusion that these apps should be written in a native framework rather than a web view. Slack is doing much mo…
You are making a false assumption that more features is something like geometripential in the amount of memory it should use. It is a list, with some images. They have Rubegoldberged themselves into some Sisyphusian box of poo while they expect us to row the SS Honeybucket to work and back. You know what my solution is for when I need to slack? I RDP to a VM running Slack. Mother of Lord! How about Slack sell lil USB…
Re: Migrating Slack's Desktop App to BrowserView
#67I'm a proponent of Electron for startups just getting off the ground with cross-platform desktop apps. Slack has raised some serious capital, however. The desktop app is the cornerstone of their product and performance is a known pain point (cpu/memory). Why haven't they left electron in the dust and taken performance seriously?
Re: Migrating Slack's Desktop App to BrowserView
#68Earlier quoted context omitted.
In year 2000 you might only have to care about Win98. And that’s it. In 2017 there’s no tech stack that lets you write consistent UIs across multiple platforms. Except, unsurprisingly, Electron
I don’t want the UI to be consistent, I want it to be platform native.
Re: Migrating Slack's Desktop App to BrowserView
#69As a Linux laptop user, I fully endorse Electron. There’s so much more available for Linux because of it that would have no client at all otherwise. Between NVMe disks and the ability to have 64gb of RAM if I want...keep it coming. I’d rather have heavy software than no software.
Same here, it's really nice to have VSCode, atom, slack, etc. RAM is pretty cheap, I'd rather put money towards a better Linux machine than give that money to Microsoft for the OS.
Re: Migrating Slack's Desktop App to BrowserView
#70What the hell is taking up all that RAM? Slack is using over 800MB of RAM on my computer right now, and it's completely idle. I've got a C# process on my computer right now handling thousands of messages per second and consuming 1/20th the RAM. If you rebuild Slack in Xamarin you'd probably drop your RAM consumption to under 50MB, just a guess. JS fiends are gonna tell me C# ain't JS, and I agree. TypeScript ain't JS…
TypeScript transpiles into some target JS version (ES5, ES6, ES2016, ES.Next). It is a different language but it gets executed as JS.