120 MByte and not even capable of doing what a similar 1 MByte tool can do. Etcher is based on Electron. A browser(engine) isn't the most optimal software for many tasks (as are web-interfaces, but that is another rant), but Electron does just that. Haven't verified it, but I also read somewhere that Electron does collect a lot of telemetry data from systems it runs on.
Generic coding and using a sort of VM to run that code on every available platform. That is the Java concept. And while that has been a pretty successful concept, especially in the workplace, it didn't catch on with consumers over the years. And now that Oracle owns Java, I don't expect a bright future anymore. But Electron seems hell bent on using the same concept, but using a browser(engine) and javascript. Both known for using a lot of computing resources in not so efficient ways when compared with code written directly for the platform the application needs to run on.
The amount of resources Electron uses, the need or want of coders to only see Electron as their hammer to solve their (computational) problems with...it all feels so inefficient and 'bloated' to me. Almost like an unwillingness to do a bit more effort and create optimized code. After all, code is created once and used many times on many computers. Better make it as efficient as possible when it is still in the hands of the coder, so all it's users don't have to spend (time/energy) when the code actually runs. Because when code runs efficiency decreases run-times, which makes processes as a whole run faster. And time is money. Offset against the cost of running software, the costs for developing platform-specific software are a pittance.
Sorry, ranting again.
