Hacker News new | past | comments | ask | show | jobs | submit | bztzt's comments login

Microsoft's head of marketing at the time posted about this on internal Yammer. He said there were two main reasons: first, "Windows 10" just did better in focus groups than Windows 9 or other alternatives; second, since the plan at the time was for all future changes to be delivered as updates rather than a newly branded Windows release†, it felt better to end on a round number.

† btw, what became Windows 11 started development as just another Windows 10 feature update, and what gets branded as a "new release" vs an "update" is mostly a marketing decision.


> what became Windows 11 started development as just another Windows 10 feature update, and what gets branded as a "new release" vs an "update" is mostly a marketing decision.

The move from Windows 10 to Windows 11 came with some pretty severe restrictions on supported hardware, so the version jump in this case makes sense to me. It would be a lot more difficult to push an "update" which obsoleted so much hardware like that.


> came with some pretty severe restrictions on supported hardware

That's hardware, and just like with the Linux kernel you have some tough choices to make about what you continue to support. Apple rendered my Intel Mac Mini a brick because despite having a 64 bit CPU its BIOS/UEFI or whatever was 32 bit and I was stuck with MacOS 10.6, no way to upgrade to 10.7 Lion.


The 10 -> 11 bump also coincided nicely with the Mac OS X -> 11 bump.


switching between a touchscreen and mouse is no more awkward than switching between a keyboard and mouse, imo


I'm not sure there's any crisply definable bright line separating them. Generally embrace/extend strategies do involve trying to make extensions that some people will consider valuable.


WinRT doesn't depend on the CLR at all, it's just an updated COM-based model.


Aren't your two paragraphs really two ways of saying the same thing?


no, but they've introduced a bunch of versions of it under different names (WPF, Silverlight, Phone Silverlight, WinRT XAML, UWP), a few of which broke compatibility, so that's probably where you got that impression.


voice is just an input method. a natural language interface can also support typing or other inputs.


The meaningful difference is whether there are isolation and distribution/update mechanisms so that users can install and maintain apps with less risk and hassle. This doesn't have much to do with (in-app) UI per se, though.


These benchmark articles frustrate me because I rarely feel they tell me anything. What do the benchmarks actually measure? When one tested product benchmarks as better/worse than another, what specifically is happening to make it better or worse? I feel like a good technical reporter ought to be able to dig deeper, do some investigation and provide real insight.


Yes


Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: