It's not necessarily hostility. We considered different updating approaches with our legal IDE where security, stability, etc. are paramount, and having a buggy application out in the wild is user-hostile. Sure, in a dream world we'd say "don't ship until it's perfect", but that's just not realistic.

We considered the daemon thing, but ended up with a hard-update check on every boot. It's thus a user choice: if you don't like the automatic updating, you can just not run the application anymore.

And even with all that, it's hard to stay on the right side of AV algorithms, etc.

We wrote about it here: https://tritium.legal/blog/update

▲

TeMPOraL 4 hours ago | parent [-]

> It's thus a user choice: if you don't like the automatic updating, you can just not run the application anymore.

That's not a choice. It s just what most apps do these days, but it's the first time I've seen anyone stating this so directly, or trying to frame it as a choice.

(And behaviorally, this makes your product just a SaaS website with extra steps.)

	▲	piker 4 hours ago \| parent [-]
		I guess I mean it's a choice in the sense that it's a transparent part of the product that one chooses how and when to use (or not). That's opposed to something running in the background on its own schedule, with its own agenda whether the user is running the application or not. [Edit: yes, that is kind of the idea. Native version has better features because it can access them.]