You do realise that I was writing about the update cycle of an ongoing project not downloading a finished product don't you?
It's crazy to have to download 4 GB of program files every time a piece of software gets altered, minimally, duplicating almost every file (> 95%) already installed simply to include a relatively small number of altered/additional files (<5%). That's akin to having to download the whole Windows operating system, over and over, every time some small part of it changed which would be crazy, ridiculous and incredibly bad practice as far as any kind of software was concerned. No engineer worth his/her salt would accept massively unnecessary redundancy on such a scale nor foist it on users. Maybe you would be happy to download gigabytes of duplicate files, over and over, unnecessarily but in my experience most people wouldn't be and I'm absolutely sure that NLT would not expect his/her customer base to have to do this on a regular basis in any case. (Nobody that talented could possibly be so stupid.) In fact I would go so far as to bet the farm that NLT will be providing incremental updates to his customers, in the same way as every other responsible software vendor does, so that his/her/their clients are neither inconvenienced nor forced to waste bandwidth unnecessarily.
I'd put money on it.
The auto-updater will almost certainly be for Windows only because it chimes with Microsoft's ethos to get Windows and the software that runs on it to do all manner of things on behalf of users whether they have agreed to it or not. (While creepily sending back all kinds of telemetry about what Windows 10 users have been doing to Microsoft headquarters for analysis.) That kind of intrusion isn't acceptable to me personally but each to his/her own, and, as you say, the overwhelming majority of PC users do use Windows because PC vendors sell new PCs with Windows already installed on them.
There but for the grace of God, go I.
