381–390 of 423 posts
Earlier quoted context omitted.
As I recall, it’s an Electron app. I just checked and the current version of Google Chrome is 635 MB, with its DMG being 224 MB. So yes, it’s insane, but easy to see where the size comes from.
Tauri has been a thing for a while, it baffles me people still choose Electron without a good reason to do so. Also webapps are just great nowadays most OS support install PWA's fairly decently no? ffs
Earlier quoted context omitted.
People complaining about 5 minute update checks hopefully don't use Windows 10/11. A while ago I did some rough calculations with numbers Microsoft used to brag about their telemetry, and it came out to around 10+ datapoints collected per minute. But probably sent in a lower frequency. I also remember them bragging about how many million seconds Windows 10 users used Edge and how many pictures they viewed in the Phot…
Try installing Adobe's Creative Cloud and/or any of its related products. I ultimately setup an instance of AdGuard just to block Adobe's insane telemetry traffic.
Earlier quoted context omitted.
So your conclusion is all software that polls is badly designed? Keeping a TCP socket open is not free and not really desirable.
Most platforms offer other notification channels - ie. Web push. Those truly are free.
Earlier quoted context omitted.
So looks like the app itself is about 10MB but there are multiple copies of it, a bundled ffmpeg and all kinds of crap like wallpaper?
I'm not sure why there are both app.asar and app.asar.unpacked. I did just run `npx @electron/asar extract app.asar` and confirmed it's a superset of app.asar.unpacked. The unpacked files are mostly executables, so it may have something to do with code signing requirements.
Earlier quoted context omitted.
> their software also downloaded a 250MB update file every five minutes How on earth is a screen recording app 250 megabytes
>> their software also downloaded a 250MB update file every five minutes > How on earth is a screen recording app 250 megabytes How on earth is a screen recording app on a OS where the API to record the screen is built directly into the OS 250 megabytes? It is extremely irresponsible to assume that your customers have infinite cheap bandwidth. In a previous life I worked with customers with remote sites (think mines…
Earlier quoted context omitted.
IIRC, Every 5 minutes used to be the standard interval between email checks, back in the days of dialup and desktop email clients. How the times have changed ..
And because how expensive they were in Portugal, I never done it, it was always on manual.
The "send and receive" button is seared into my brain
I was in Spain at the time, and at first you had to connect to the Internet through a phone number in France.
Did you guys have something like that?
Earlier quoted context omitted.
Because developers can suck. I work with developers in SCA/SBOM and there are countless devs that seem to work by #include 'everything'. You see crap where they include a misspelled package name and then they fix it by including the right package but not removing the wrong one! .
The lack of dependency awareness drives me insane. Someone imports a single method from the wrong package, which snowballs into the blind leading the blind and pinning transitive dependencies in order to deliver quick "fixes" for things we don't even use or need, which ultimately becomes 100 different kinds of nightmare that stifle any hope of agility.
> Someone imports a single method from the RIGHT package
and hundreds of megabytes come in for what might be one simple function.
Earlier quoted context omitted.
Most platforms offer other notification channels - ie. Web push. Those truly are free.
No, those are abstraction over a TCP socket and introduce more complexity than you'd need for something like this. There's nothing wrong with occasionally polling for updates.
Your app can also be ready to receive notifications even when the app isn't running - using zero RAM. Inetd on Linux allows similar stuff (although no ability to handle ip changes or traverse NAT makes it fairly useless in the consumer world).
This stuff is important because polling dominates power use when idle - especially network polling which generally requires hundreds of milliseconds of system awakeness to handle tens of network packet arrivals simply for a basic http request.
Did you know, a typical android phone, if all polling is disabled, has a battery life of 45 days?
Earlier quoted context omitted.
What's wrong with checking for updates upon start once (and cache per day) For me that would also be wrong, if I cannot disable it in the configuration. I do bot want to extend startup time.
Wait until you learn about non-blocking IO. And threads. It's a whole new world out there.
Earlier quoted context omitted.
No, those are abstraction over a TCP socket and introduce more complexity than you'd need for something like this. There's nothing wrong with occasionally polling for updates.
Web push, FCM, APNS, etc are free because they only have a single systemwide TCP channel open - and that channel is already open whether or not your app chooses to use it. Your app can also be ready to receive notifications even when the app isn't running - using zero RAM. Inetd on Linux allows similar stuff (although no ability to handle ip changes or traverse NAT makes it fairly useless in the consumer world). This…