this post was submitted on 22 Jan 2026
997 points (99.2% liked)
Greentext
7633 readers
909 users here now
This is a place to share greentexts and witness the confounding life of Anon. If you're new to the Greentext community, think of it as a sort of zoo with Anon as the main attraction.
Be warned:
- Anon is often crazy.
- Anon is often depressed.
- Anon frequently shares thoughts that are immature, offensive, or incomprehensible.
If you find yourself getting angry (or god forbid, agreeing) with something Anon has said, you might be doing it wrong.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
A guy at work wrote a script to automate something for a department. The script was, I don't know, sub-100 lines of JavaScript. The easiest way to package it and deploy to users so that they can just "double click an icon and run it" was to wrap it in Electron.
The original source file was 8 KB.
The application was 350 MB.
Could he not have packaged it as a .HTML file?
Well, I don't think our antivirus would let that through anyway. But the reason we wanted an .exe is also because then I could pack it as Intune-deployed package and make it available for the users that work on the thing it's automating (there were still some manual steps needed in the process).
Deploying an in-house built .exe solves the problem of the .exe not being certificate-signed, so things like SmartScreen stop blocking it.