4 ms·
What is this ridiculous obsession with executable size? How much time did this author spend chasing down alternatives to a measly 120MB? If they're working on a
by lmm 8y ago
What is this ridiculous obsession with executable size? How much time did this author spend chasing down alternatives to a measly 120MB? If they're working on art project then fair enough, but if they're working on a useful program then surely anything else they could have done with that time would have brought more value to end users than shaving off 3 cents' worth of disk space.
- krageon 8y agoHow is 120MB in any way, shape or form "measly"? It is exactly this kind of thinking that delivered unto us the absolute monstrosities we see in the wild.
- badsectoracula 8y agoThis sort of "who cares" thinking gives us lazy bloatware like Electron.
- lmm 8y agoAKA useful software that actually does something users want, rather than some kind of ascetic practice exercise. Yes, yes it does.
- gmueckl 8y agoWell, not really. I hate on Electron not because of its size on disk, but its runtime memory footprint. Things like Skype in the background using 500MB, an Autodesk update notifier sitting silently in the tray using 350MB etc. all add up to a few GB of main memory you suddenly don't have. And these numbers are real, by the way.
- Justsignedup 8y agoThat's kinda the fault of the developer. Electron itself isn't very large and I've seen very well crafted electron apps. The fact that slack uses 1-2gb memory is definitely on slack.
- blattimwind 8y agoIt's kinda weird how little you have to do with 32 GB (!) of RAM until Windows starts to complain about not having enough free memory and you-better-close-some-applications-right-now! I remember when a 1 GB memory upgrade was something, and back then I could even play a game on 512 MB of memory and occassionally alt-tab to a web browser for cheats... nowadays a web browser on 512 MB RAM is virtually impossible. (Edit: I realize this complaint is quite old, but from the age where hundreds-of-MB main memory were mainstream we have seen very little actual improvement in GUI fancyness, yet a massive explosion in CPU and memory use, and often even heavily deteriorated responsiveness. That doesn't hold going from the "couple of megs" to "hundreds of megs" age.)
- astrobe_ 8y ago> nowadays a web browser on 512 MB RAM is virtually impossible. Right now my Palemoon browser uses less than 240Mb. It is possible, just don't do stupid things (like keeping 4385972Z38947 tabs open instead of using bookmarks) or cut out a little the eye-candy and the the "geek status symbol" stuff.
- TelmoMenezes 8y agoEarth's resources are not infinite, nor its ability to tolerate pollution. Less importantly, my computer's resources are also not infinite. Yes, maybe your Electron app does something I want, but guess what, there are numerous other things I also want to do, and it is a bit silly that an IRC replacement now takes half of my computing power and manages to be less responsive than the stuff I used 20 years ago, in the computers of 20 years ago.
- saagarjha 8y agoElectron doesn’t actually do what I want: I want apps that fit in with the rest of my system and don’t use excessive resources.
- badsectoracula 8y agoNo, lazy bloatware like Electron isn't necessary to create useful software that actually does something users want. These two are independent of each other, you can create useful software that actually does something users want and still have it be lightweight on resources and fast.
- BubRoss 8y agoI don't consider text editors that take 10,000 times the necessary resources to run without lag to be useful.
- deleted 8y ago[deleted]
- lmm 8y ago> If personal storage units were given away for free, you might argue that it doesn't make sense to organize your stuff, or remove stuff you don't need anymore, and you would be wrong. The least important reason to consider is to conserve disk and bandwidth; the most important is to reduce risk by reducing surface area. Small, sleek and efficient is mostly about reducing cognitive load, even if it had it's roots in mechanical resource conservation. I agree with that much, but using GTK+ in the normal way for your language has a much lower cognitive load than any proposed alternative. > BTW I work on a project that made this same argument years ago, writ large, for the CI system they built. "Size doesn't matter; just throw more money at instances; its cheaper than spending dev resources to make it efficient." So, now we have a development pipeline that uses more EC2 instances than production, by a factor of about 100. The build no longer runs well on (very fast) dev machines, and takes 30 minutes even on xlarge instances. The build is enormous, complex, and slow, and it was allowed to get that way because someone made the same argument you are making against a strawman. That's a textbook slippery slope fallacy. If and when resource consumption becomes a significant issue for your use case, take measures to address that. Size absolutely can matter. But 120mb does not matter.
- cfv 8y agoThe King James bible is about 4mb of UTF-8 text. If your business code is 300k, or about 1/13 of that, then slapping a whopping 30 bibles of bullshit you will definitely not use for a 2 pane thing with a couple buttons and some renderer output on one side is not an insignificant investment.
- lmm 8y agoWhy? Is a medieval scribe hand-copying your GUI libraries? A bible costs maybe $15, which is about 60GB's worth of storage - that seems like a more relevant comparison.
- alxlaz 8y agoIt's not ridiculous. We write off executable size as something that's irrelevant in an age where you can get a 4 TB drive for (what most of the HN audience would consider) peanuts, but it's not just disk space budget that's affected. Larger executables also mean: - Longer start-up times (ridiculous things in 2019: a) SSD prices, b) the fact that it takes longer for an Electron todo app to load off a high-speed SSD than it took for basically the same application to load off my old Amiga's floppy drive) - Fewer applications that you can run at the same time, higher chance of disk thrashing when resuming from suspend (bloated frameworks still have to make it to RAM, which yes, is also cheap and abundant, but load up a few VMs and see how abundant it seems then) - Additional bandwidth used for delivering application updates - Higher battery consumption if you use antivirus software and the like, because all those bits still need to be looked at. - Sometimes it's just security theater, but not always -- a complex framework still has an attack surface even if your application doesn't use all of it. These things save way more than a few cents' worth of disk space.
- lmm 8y agoSure. However long it takes to read 120mb off a disk (most likely less, if the application is only using some of the GTK dlls). 120mb of RAM. 120mb more to read when restoring from suspend. 120mb extra data use over your home internet connection. (I'm not going to talk about antivirus time because if you're using antivirus in 2019 you deserve whatever happens to you). It's still all irrelevant. Put a monetary or human-time value on it and compare to the cost of the application, or the development time, or a single crashing bug. Our programming culture's priorities are so far skewed from whats' actually important.
- xfer 8y agoAll that multiplied by the number of customers. If you don't value your customers, then they are all "irrelevant". > Our programming culture's priorities are so far skewed from whats' actually important. Indeed, that's why there are so many electron based bloatware being developed.
- 8y ago
- swiley 8y agoBelieve it or not there are countries where people trade sex for power to charge their phones. I'm sure the resources wasted by bloated apps are precious to them.
- sesteel 8y agoElectron usage has forced me to spend some of my yearly dev budget on a 32GB machine; this comes to an extra $400 if purchased preinstalled. Now, had I not relied on so many Electron apps I probably wouldn't have required a new laptop at all. Memory management (or what I like to call memory hygiene in cases like these) is a concern. For far too long developers have brushed aside the memory usage of their applications not thinking of the cost on their end users. This has real negative effects on the user experience. This isn't confined to Electron though; many other apps also use an enormous amount of memory as well. It is a general problem.
- kitsunesoba 8y agoDevelopers assuming that all users have hardware and internet speeds anywhere close to as good as their own is a huge problem. Not only is there a huge chunk of people who are using low-to-midrange laptops ranging anywhere between old and ancient, but manufacturers are still selling brand new machines with CPU power and RAM roughly on par with the average laptop from 2007 (C2D class CPU, 2-4GB RAM, 5400RPM HD). Those users aren’t going away any time soon, and by casting resource consumption aside as a total non-issue, developers are also casting these users aside.
- megous 8y agoWell, just loading 120MB executable from an SD card to run it would take 6s in ideal case on the tablet that I use, before it even gets to execution. That's 10s+ startup times for Electron app. Meanwhile my 2MB static C app starts in fractions of a second right after boot. Storage space is not the only consideration. Storage speed may also be limited.
- alkonaut 8y agoFor making something absolutely HUGE like Blender or a DAW (which he uses as examples) I can't see why size makes a difference at all. It doesn't matter whether blender takes half a gig or five, or whether it starts in one second or five . On the other hand if you make a VST plugin or a chat application THEN startup time of 0.1s instead of 1s makes a huge difference. So I think size/startup time really is important, but I fail to see why he chooses these huge applications as examples (because for them it doesn't matter). I suppose he chose them as they were "state of the art" in terms of complexity etc - but perhaps he should look for smaller aps (such as JUCE plugins) to see the state of the art in terms of size/load time.