Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 17 submissions in the queue.
posted by n1 on Monday January 04 2016, @09:21PM   Printer-friendly
from the own-worst-enemy dept.

Speaking to Windows Weekly, Microsoft Marketing chief Chris Capossela explained that users who choose Windows 7 do so “at your own risk, at your own peril” and he revealed Microsoft has concerns about its future software and hardware compatibility, security and more.

[...] There’s only one problem with Capossela’s statements: they are complete rubbish. Windows 7 is no less secure than Windows 10 (it will be supported until 2020) and no less compatible with new hardware and software. In fact its far greater market share means it is developers’ priority and has greater compatibility with legacy programmes and peripherals. If Fallout 4 won’t run on your Windows 7 computer, it will be upgrading your components not installing Windows 10 which fixes that.

As for fragmentation, the only issue that creates is for Microsoft and its target of getting one billion devices running Windows 10 within 2-3 years of release.

Original article from Forbes. Article is behind annoying ads and JavaScript.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Saturday January 09 2016, @05:08AM

    by Anonymous Coward on Saturday January 09 2016, @05:08AM (#287151)

    First, all Win2K retail boxes during the 'crossover' with WinXP got silently updated to SP3, changing the license terms from the original Win2K ones to XP style ones (I forget the specifics, but a bunch of the 'we can audit your machines' licensing terms.)

    Furthermore they ensured the next version of Visual C/DirectX broke Win2k compatibility, despite no significant reasons it needed to (There were API/ABI hacks within a year or two that allowed running both XP applications and drivers on Win2K.)

    Long story short: They ensured Win2K was dead before SP5 even came out. It apparently made it up to 6, but I never actually got up to running it since all my apps had been broken for 2 years by then.