4 ms·
I get what you're saying and I totally agree with the sentiment, but in this case I can let it slide. It's the only practical way to make a cross platform app f
by andrepd 9y ago
I get what you're saying and I totally agree with the sentiment, but in this case I can let it slide. It's the only practical way to make a cross platform app for Linux, Windows and Mac. They simply don't have the resources to write and maintain (at least) three desktop apps. I can totally understand that a small company has to make compromises like writing their desktop apps in Electron.
That large companies also do this is another story entirely.
- OldSchoolJohnny 9y agoI disagree completely, a single page application can be used on any of those platforms in browser and doesn't require Electron at all.
- yebyen 9y agoIs that really improvement if you need to run a browser to run the app? I guess most of us have the browser open all the time anyway, so adding an Electron app is just one more thing, but I know that Chrome on my machine soaks up a lot more than 130MB ... I've got a lot of tabs open right now and I'm not sure how to read the memory usage in Chrome's task manager, but Chrome appears to claim to be using about 450MB just for the browser, plus some additional amount for each tab I have open.
- nine_k 9y agoHow often do you even close the browser?
- JCzynski 9y agoAnd they had one already. Which no one liked.
- 72deluxe 9y agoI worked for a company that released control software for audio hardware. I was the only GUI developer (the only guy writing the frontend app), and there was another dev who wrote firmware and a network communication library that I used in the app. The GUI used wxWidgets using C++ and included a 3D section for system layout (using OpenGL). All of the 2D GUI controls for the rest of the system were "owner-drawn" which means that they overrode the ::OnPaint and drew themselves so as to look different than native controls (as audio systems always have to "look different"). This means buttons, toggle buttons, radio controls, control surfaces, sliders, meters, compressor meters, knobs, graphs, charts, lists, grids, EQ control graphs, everything. There were no native controls other than in popup dialogs (like saving/exporting). It redraw every 50ms based on data that it was receiving over the network from a series of hardware, with this data logged and processed in background threads. It used less than 1% CPU and a fraction of the RAM mentioned here for a chat app, even with cached in-memory bitmaps that it generated in code for drawing. This ran on Mac OS, Windows and Linux. This means a native binary on each system. It can be done. It is wrong to say that this embedded-web-app way is the "only way" of doing it. Not to be rude, but it just means that the devs can't be bothered to do it another way. And that was me writing all of it, plus one guy who did the networking library. Two of us. How can they "not have the resources"?
- jononor 9y agoHow many updates did you ship per month? Web dev tends to optimize for ability to change/improve quickly (for good and bad). Resource use on the computer typically not prioritized.
- 72deluxe 9y agoWe did not ship often! Quality is more important to me than being able to quickly fling rubbish out of the door. Anyone can do that. For audio hardware, you don't want to be grabbing software + firmware updates multiple times a week. You might be on tour with the hardware and changing it whilst on the road is likely a no-no. I am now at a place where we ship daily, sometimes multiple times (different branches). The emphasis on decent code and quality is now higher than the previous place I worked. The codebase here is also incredibly vast by comparison. We can still add features quickly but it is of little use if it is of poor quality. What's the point of bad software even if it is quickly shipped?
- eptcyka 9y agoTelegram has found a way to deliver the same client on both Linux, Windows and MacOS using Qt. One does not need to consume hundred of megabytes of memory to achieve a cross-platform solution.
- mikewhy 9y agoThe telegram app for macOS is taking ~140MB of ram to display the welcome screen here.
- em3rgent0rdr 9y ago> "They simply don't have the resources to write and maintain (at least) three desktop apps." I feel Signal should have implemted the core messaging components as a non-gui program or library or plugin to another Messaging app (e.g. Pidgin). Then if they want their own app, they could have used a lightweight cross platform window toolkit (e.g. WxWidgets or Qt).