Microsoft loves to use codenames and from the past few years, there are two in particular that you may recall; Blue and Threshold. With Windows 10 (Threshold) coming to market sometime this summer, Microsoft is already starting to work on the next update for the OS.
Microsoft has said multiple times that Windows will be moving at a faster cadence than in the past and they are already working on a release for 2016. The codename for the project is ‘Redstone’, a popular item in the recently acquired game, Minecraft.
So now we know why they acquired Mojang.
Pssh. If your going to make me rifle through old memories to dig up Windows development codenames, at least hit me with Chicago, Whistler or Longhorn. If I can dig through the junk on my desk and find a DVD labeled “WinBlue” or “Win10TP”, you’re not asking me to remember anything – you’re asking me to find it. Where’s the fun in that? Where’s the challenge? Make me work for it I say.
By the way, this comment is packed with just as much new information as the linked article is. Now you all know my desk is a shithole (one thing) and that the next codename for Windows is…crap. Forgot it already. Red something. Enjoy! 🙂
Edit: Redstone. It’s Redstone.
Edited 2015-04-07 19:26 UTC
I REALLY wish we could go back to the 5-6 year update cycle. Things were much simpler then. If you had XP, you were set. Pretty much any hardware/software you bought would work. Now I guess they’re going to release a new version every year or two, probably breaking stuff in the process …
Well – the next version will supposed to be out in 2016. Windows 10 will be out around Q4 this year. That means that cycle is now not even 2 years, but 1 year. So – every year an new windows version?
I really don’t like it. This is way too fast in my opinion. Maybe time for an “Windows LTS” version?
Edited 2015-04-08 06:51 UTC
With the new Universal App Model they are going for a native runtime approach where the APIs are separate from Windows specific versions.
Basically, the applications are coded against set of WinRT APIs (COM + .NET Metadata) and should run in any platform that provides implementations for those interfaces.
Hence how they are approaching the single .exe, multiple Windows platforms.
So the actual Windows version shouldn’t matter as long as the required contracts are supported.
And what about hardware drivers? You would THINK they’d be the same, but I already ran into something that worked in Windows 7, but was a bit flaky in 8.
So that the windows might be updated using redstone blocks?
Seriously though, I’m still surprised at how drastically money can change a man.
http://www.gamespot.com/articles/notch-refuses-to-certify-minecraft…
Be honest, who among us would have been able to stick to our convictions with $2.5B on the table?