|
DJ van Wyk wrote: The topic discusses the number 9. In my view the number 8 is irrelevant in this context. To be precise, the topic never discussed 9 except in the explanation of getting from version 8 to 10. The elephant in the room is that Microsoft's versions go from 8 to 10. Base 8 isn't a good explanation for that because then it should go from version 7 to 10 in that case. However, there isn't a really good explanation for Microsoft's naming conventions. Remember Windows 99? Well, if you're 15 or less, you wouldn't. (Maybe even 20 or less.) But that'd be a good explanation for the introduction of Windows 14, not 10.
Even the "explanation" lists version 10 twice in the series, so this really should be version 11 by its logic.
The best explanation is that Microsoft's naming convention is erratic and inconsistent. Don't expect it to make sense.
|
|
|
|
|
Sorry, I don't remember Win 99, I do remember 96. I also remember Win 2000. So at one point their release names were associated to the year of release.
|
|
|
|
|
he probably means base 10, as in 8 + 1!
|
|
|
|
|
Wait until Visual Studio (15)9 comes out, all octal and hex references will have been removed to enforce the MS paradigm.
|
|
|
|
|
So, when there will be base-9 notation support?
|
|
|
|
|
Gosh, I hadn't thought it through that far. I'm sure it will be included in the VS (15)9 release - but perhaps someone with more free time than sense could bang a VS toolkit add-in together so we could get some early practice....
|
|
|
|
|
9 is, amusingly, a 4 anyway.
|
|
|
|
|
I thought it was because they wanted to avoid the possibility of Apple commercials with a frantic Hitler
yelling "Windows!!! Nein!!! Nein!!! Nein!!!"
|
|
|
|
|
Now that[^]... is the real reason!
|
|
|
|
|
I think the interwebs may have figured out the true reason, yes. Seems all to believable (and those code search results make it more believable).
TTFN - Kent
|
|
|
|
|
|
How can they be so sure that all ...
if(version.StartsWith("Windows 1"))
... code is already out of production
modified 19-Nov-18 21:01pm.
|
|
|
|
|
That's a damn good question you just raised here!
|
|
|
|
|
The languages that included the .StartsWith method didn't exist until later. Also, the installers for those programs are all 16 bit installers and won't run on current versions of Windows.
|
|
|
|
|
they should name it windows me 10
.'\ /`.
.'.-.`-'.-.`.
..._: .-. .-. :_...
.' '-.(o ) (o ).-' `.
: _ _ _`~(_)~`_ _ _ :
: /: ' .-=_ _=-. ` ;\ :
: :|-.._ ' ` _..-|: :
: `:| |`:-:-.-:-:'| |:' :
`. `.| | | | | | |.' .'
`. `-:_| | |_:-' .'
`-._ ```` _.-'
``-------'/xml>
|
|
|
|
|
Just wondering ... seeing all the hype about it being SSSSOOOO "wonderful" ... did they think of it i.t.o. "It's a totally 'new' windows - like in Windows 2.0"?
...
And then realizing: "That's already been used"
...
And then some "brilliant" meeting participant "remembering" that "computers count in 1s & 0s" ... I can just imagine the sort of meeting (having had several of those myself - ending in me just hanging my head)
|
|
|
|
|
I thought that myself, but then I realized that Intel processors are little-endian. Which would make it "Windows One", surely?
|
|
|
|
|
Exactly! That's one of the reasons I'd have just hung my head in that meeting ... not worth shaking!
|
|
|
|
|
I think a lot of people are misreading it as "Windows Ten". It's clearly "Windows Two".
|
|
|
|
|
It's a binary number and part of the new low-numbering scheme. XBOX ONE, Windows TWO. Makes sense.
|
|
|
|
|
So then you mean we can expect a 360 / 365 in the future (or should that be past)?
|
|
|
|
|
|
Good point! No counting of any chickens allowed (especially not with Microsoft's invention of a new numbering system)!
|
|
|
|
|
M$ may find themselves in court again if they claim to have invented binary numbers! I'm pretty sure that claim has already been made by Apple and Samsung!
|
|
|
|
|
Windows 10 ie- Starts with a 1 (positive) and ends with a 0 (non-positive)- if it really follows Win8
Hope it is more like a TEN- sportslike lucky number for all
|
|
|
|