News for hackers. Stuff that matters.
Re:Airpass – easily overcome WiFi time limits by tucnak on Sunday June 22, 2025 @04:50PM (#44350175)
The proposition that Electron apps are somehow "saving time" is preposterous!

Of course, the real cost-saving is in labour—web development presents a radically lower barrier to entry compared to even non-native, cross-platform UI/UX platforms such as Qt, or Flutter, or what-have-you, let alone simply managing multiple native applications.

So this is not a bill-of-materials kind of analogy, it's a statement about talent.

Web leaders have grown complacent; at times, it seems they don't take things seriously. I mean, just take a look at something like SvelteKit. I'm not a web developer, however I happen to like Svelte a lot, but also despise SvelteKit equally as much.

Every major release is like "fuck you."

Re:Airpass – easily overcome WiFi time limits by _gruntled on Sunday June 22, 2025 @05:40PM (#44350533)
“every major release” lol you mean the single major release that has ever happened since GA?
Re:Airpass – easily overcome WiFi time limits by tucnak on Tuesday June 24, 2025 @12:11PM (#44367738)
*s/major/minor
Re:Airpass – easily overcome WiFi time limits by fwip on Sunday June 22, 2025 @05:05PM (#44350270)
Yes, the savings in labour translates to savings in time. This should be obvious.

Using Electron to package your application often saves time over writing a native app.

Giving a regular user a ready-to-use app saves them time, because they aren't googling "how to use terminal" for five minutes or trying to copy-paste the magic command out of their notepad app.

Re:Airpass – easily overcome WiFi time limits by tucnak on Tuesday June 24, 2025 @12:16PM (#44367793)
> Yes, the savings in labour translates to savings in time. This should be obvious.

Under some circumstances; arguably, in only a handful of circumstances. The colloquial 10xer may as well as get the job done at a fraction of the labour cost associated with a 10-man senior (but really, comparatively junior) team, whereas the latter would spend months rewriting, refactoring, troubleshooting, triaging, bug-hunting, what-have-you...

Much can be said about inefficiencies of engineering teams.