From: nospam <nospam@nospam.invalid>
Subject: Re: A simple way to transfer photos from your phone to Windows without installing anything on either
Full headers:
From: nospam <nospam@nospam.invalid>
Subject: Re: A simple way to transfer photos from your phone to Windows without installing anything on either
Date: Tue, 27 Feb 2018 15:26:31 -0500
Organization: A noiseless patient Spider
Lines: 49
Message-ID: <270220181526318669%nospam@nospam.invalid>
References: <1pat6bvdosd5h$.1v0zueckye1z0$> <N8CjC.87760$CZ2.56323@fx39.iad> <k1708hh1x1bm.4u71bsj0gbj3$> <p6n7mu$cuh$> <19gis5r2t3woe$.15ka8hlpcnip0$> <9K3kC.89577$CZ2.67163@fx39.iad> <1dxxhzinci9qd.hpx5dw75usol$> <p6r6ge$5f4$> <acakC.112774$mJ1.26756@fx13.fr7> <p6s785$nht$> <v9lfsboe3dmc.1o44r2zk1zgx8$> <p6t8p7$ckt$> <240220182343565132%nospam@nospam.invalid> <1xbui2c4r8cc2.hlcsh95dc0q$> <260220182258584968%nospam@nospam.invalid> <b3r1pb4p9fea$.mvm960z2aw29$> <270220180216183298%nospam@nospam.invalid> <18sbi2qwkqlde$> <270220180537565668%nospam@nospam.invalid> <12fh4vymm2iv$.1c6konrssjq94$> <270220181349510679%nospam@nospam.invalid> <glu3qikmm04z.fm2hhk76lg89$>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Injection-Info:; posting-host="3ff3cd690d33a67a3e982f56b17f2a55";
logging-data="16661"; mail-complaints-to="";posting-account="U2FsdGVkX18xoEm6ZbxqiSQGWrYRS/JC"
User-Agent: Thoth/1.9.0 (Mac OS X)
Cancel-Lock: sha1:tj0AW8mSCTNT5bqJsaDNXa5ExTE=
Print Article
Forward Article
In article <glu3qikmm04z.fm2hhk76lg89$>, ultred ragnusen<> wrote:

> >> So I was able to do the impossible, for a while, which is stave off the
> >> Windows 10 Pro updates.
> > 
> > that's a very, very stupid thing to do. you're not getting bug fixes,
> > security patches and new features. 
> The answer to that objection is that if I had wanted Microsoft updates, I
> would have loaded them on my own. 

that's not an answer. it's an excuse for foolishness.

> Just like I do with my iPads to prevent the diarrhea

moving goalposts to trolling.

> >> I suspect Microsoft never coded the if-then-else to handle jumping from
> >> Windows 10 Pro Version 1511 OS Build 10586.1106 to the 16299 Upgrade from
> >> November 2017 (1709 release).
> > 
> > since just about nobody is in that situation, there's very little
> > reason to bother. 
> It's a classic coding rule to abort gracefully when the unexpected occurs,
> which Microsoft did - for years - but not recently.

there's no way to cover every possible situation.

rare ones, particularly ones that are the result of users going out of
their way to break things, are not a high priority.

in fact, they're best ignored. anyone circumventing the normal update
process should know the risks they're taking and be able to deal with
the inevitable problems that will occur.

> > there are far more important problems to address, ones that affect many
> > more people. 
> You have the tunnel mindset of the classic Silicon Valley coder, where I
> know hundreds of them, perhaps thousands. You have no concept of how to
> code properly to handle exceptions if you actually believe that.

ad hominem.