71–80 of 214 posts
Earlier quoted context omitted.
Messages.app does all of those and uses a tenth of the RAM.
Yeah, but it doesn't run on my PC, or my phone, or in a browser.
Earlier quoted context omitted.
TypeScript transpiles into some target JS version (ES5, ES6, ES2016, ES.Next). It is a different language but it gets executed as JS.
I think, that he was trying to say, Typescript feels like C#, so why not use the more performant option, if you use something similar but slower anyway.
EDIT: Not defending Slack's choice of JS, or the consequences of that choice on its memory footprint, CPU utilization, or excess consumption of my battery in any way, but it's not purely a matter of "which one is the most efficient/performant/whatever?".
Earlier quoted context omitted.
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…
> there's often reasons to reinvent a portion of an API 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.
The rest of the apps I find myself using don't use those same UI/UX patterns/designs, and I don't think it matters that much: Photoshop, Terminal, Telegram, Bear, Fantastical... the list goes on. The applications that keep me coming back are the ones that are smooth and don't interrupt my train of thought (most everything here), or have some big use case (Photoshop) that keeps me coming back.
I'll also point out one more time that Telegram is what people bring up every time this discussion rolls around, so they're clearly doing something right and people must not think it looks _that_ out of place.
Hell, I'd argue that the consistency of UI/UX on Apple products matters more for the initial purchase and wow-factor than it does once a user has settled into their environment. Every application does not need to function and look exactly the same.
To be honest, this all feels like moving the goalposts, and is why I usually refrain from getting into these discussions.
What 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…
I'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?
Slack can take performance seriously and stick with Electron. That's certainly what this very article is about: big steps towards better performance.
Slack switching to something like Qt would (maybe) fix Slack, but then we would still have many slow Electron apps.
Earlier 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
https://news.ycombinator.com/item?id=14066784 . Here's a discussion on alternatives. It's really not the only choice.
Earlier quoted context omitted.
TypeScript transpiles into some target JS version (ES5, ES6, ES2016, ES.Next). It is a different language but it gets executed as JS.
I think, that he was trying to say, Typescript feels like C#, so why not use the more performant option, if you use something similar but slower anyway.
I'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?
I won't use the desktop app because I have standards. But apparently we're too few in number to matter. And from a business perspective there's nothing wrong with that. Frequently what engineers want and what makes (good business) sense are different.
Earlier quoted context omitted.
That's why I'm developing eul, a lightweight native desktop client for Slack, Skype, Facebook etc: https://eul.im It's only 4 MB and handles tens of thousands of Slack messages in one chat without lag. 1.0 release is going to be out in early November.
This sounds promising :) Btw, you have a Gmail icon on your site -- I'm assuming that implies Hangouts support?
No, it supports Gmail via the Gmail API. Soon it's going to have a full email client built in.