They've always plan things in advance, the only thing that changed this time is the fact that everyone thought that Windows 10 codename will change after 2 waves (TH1, TH2, RS1, RS2) .hounsell wrote:Yeh, they're definitely planning something beyond RS2 already. I can't confirm it as "RS3", but it seems to make sense to me from what I do know about it.
Of course you can run Server OS as a Desktop OS..hounsell wrote:Yeh, they're definitely planning something beyond RS2 already. I can't confirm it as "RS3", but it seems to make sense to me from what I do know about it.
I don't buy this whole "focused on mobile" thing though. I think this is a message Microsoft have implied repeatedly by saying RS1/2016 is "not focused on mobile". I think they imply it not because 2017 will be, but to discourage people from asking awkward questions about how more people think the earth is flat than think Windows 10 Mobile is a viable platform.
ARM64 is coming, but I'm still going to insist, as I did in this article about ARM64 support in Redstone, that the more advanced ARM64 project is in the Server division, not Mobile. And you can safely ignore any crackpot that mentions ARM/ARM64 and the desktop.
Or if you have DreamSparkmadalin88 wrote:If you have the money to buy a Server license for Desktop use
...or if you simply happen to be privileged enough to obtain a copy from the FTP server.madalin88 wrote:If you have the money to buy a Server license for Desktop use
That involves the version being abandonware.DJ Deedahx wrote:...or if you simply happen to be privileged enough to obtain a copy from the FTP server.madalin88 wrote:If you have the money to buy a Server license for Desktop use
That's the surprising thing.Zacchi4k wrote:I think we won't get any official news at least until RS2 development begins
That's the idea behind windows as a service. You won't see a huge change update to update but over the course of a few years it might feel like a new os without that initial "everything is different, I hate it" shock. Just think if xp was a service, you might see some complaints about how xp doesn't look and feel like it did 15 years ago but they would probably be few and far between. I personally think it is a smart move by Microsoft but I can understand why some might be annoyed by it.Roo_the_Vickty wrote:Big deal... This so called updates with fancy names are crappy versions of service packs
It is not even a new os...
Windows 10 is NT 10.0.Roo_the_Vickty wrote:how is it smart when you redownload whole OS again?
it is just facial make up to call it service...
by that you would still be at 6.2 kernel with repatched component by component
and not entire OS
It's smart when you go to do a clean install. Instead of having to apply every patch since release, all you need is the latest build and cumulative update, plus some little things here and there.Roo_the_Vickty wrote:how is it smart when you redownload whole OS again?
it is just facial make up to call it service...
by that you would still be at 6.2 kernel with repatched component by component
and not entire OS
wrong, its 6.3Zacchi4k wrote: Windows 10 is NT 10.0.
I disagree! It's a huge difference: remember for example when You had SPs on Win XP and had to go to Windows Update and get 500 - 1 GB or more of updates than you have to check for updates again, cause there were updates for updates and so on.Roo_the_Vickty wrote:Big deal... This so called updates with fancy names are crappy versions of service packs
It is not even a new os...
And how is this different from now?How would it help you if MS would release new OSs every year and you have need to buy new licenses every year
Yes, that is exactly why both th2 and rs1 are bumping the build number... would be nice if you knew how the current servicing model works.Roo_the_Vickty wrote:Big deal... This so called updates with fancy names are crappy versions of service packs
It is not even a new os...
