Slashdot Mirror
Lost Opportunity? Windows 10 Has the Same Minimum PC Requirements As Vista
MojoKid writes Buried in the details of Microsoft's technical preview for Windows 10 is a bit of a footnote concerning the operating system's requirements. Windows 10 will have exactly the same requirements as Windows 8.1, which had the same requirements as Windows 8, which stuck to Windows 7 specs, which was the same as Windows Vista. At this point, it's something we take for granted with future Windows release. As the years roll by, you can't help wondering what we're actually giving up in exchange for holding the minimum system spec at a single-core 1GHz, 32-bit chip with just 1GB of RAM. The average smartphone is more powerful than this these days. For decades, the standard argument has been that Microsoft had to continue supporting ancient operating systems and old configurations, ignoring the fact that the company did its most cutting-edge work when it was willing to kill off its previous products in fairly short order. what would Windows look like if Microsoft at least mandated a dual-core product? What if DX10 — a feature set that virtually every video card today supports, according to Valve's Steam Hardware Survey, became the minimum standard, at least on the x86 side of the equation? How much better might the final product be if Microsoft put less effort into validating ancient hardware and kicked those specs upwards, just a notch or two? If Microsoft did raise the specs a notch or two with each release, I think there'd be some justified complaints about failing to leave well enough alone, at least on the low end.
If you want the PC that you've been using for the past 5 years that works perfectly well to stop being able to run the latest version of its OS well then it would be a Mac.
I think the reason the specs aren't increasing much is because the pace of hardware improvements isn't moving as fast as it used to. Nowadays, you pick up an i7 and 16Gb of RAM, your favorite video card, toss an SSD in there and you've basically hit the limit.
All we're getting these days is more cores as the whole gigahertz wars ended 10 years ago.
"Freedom in the USA is not the ability to do what you want. It is the ability to stop others from doing what THEY want"
Windows is an operating system. It's job is to allow other applications to be executed simultaneously. All of the resources windows consumes are resources denied to other applications. I'm not saying that we need to be stingy like in the bad old days when programmers where more concerned about saving clock cycles than writing scalable, maintainable, and reusable code. But now that we are passed all that, there is no sense in wasting cycles frivolously. Let the applications do that.
Since when is having a light-weight OS a bad thing? Haven't people been harping on MS enough for having bloated OSes?
Sure, make allowances for multiple-core and multiple CPUs on the not-so-low end, but making the minimum requirement a single CPU was definitely smart on their end.
I am working for a company with 6000+ desktops. I do not understand why our client engineering is rolling out faster hardware every year. 95% of all office workers need MS office, a browser and email. Most of the home users just need a browser these days. Those core i7 are just idling around heating office space.
I have now started rolling out 200 dollar desktop hardware (zotac). Which could really become a problem for microsoft. The windows licence price tag looks really expensive with these hardware prices.
Office problems are solved, we do not need faster hardware. And microsoft is manly making money from, *drumbeat*, office workers.
Best
-S
You're not really "giving up" anything. You don't turn on the computer to play Operating System. You do it to run applications. So Windows requires a low overhead? Well that's great, an operating system SHOULD have a low overhead because it's supposed to get out of the way, not use resources. Your computer is a zero-sum game, memory and CPU that is taken by the OS is usually unavailable to your apps, the things that are actually important (barring, of course, apps that don't multi-thread and can only use part of the CPU, etc).
I suppose we have this fantasy of rotating windows, whiz-bang effects, SFX on the window borders on the desktop.. what do you really get from that? Anything beyond saying "oh that's cool" when you see a demo on the store shelf or a flashy yet impractical interface on a TV show? I know what I got from that -- an annoyance with Gnome 3, GPU memory reserved by the f*%^ing interface, and a lot of time spent figuring out how to turn that nonsense off (thank God Gnome's extensions make that easier to do that now than it was a few years ago!).
Maybe a simpler interface is better. Maybe an interface that doesn't try to do too much visually results in a more USABLE experience. More bells and whistles are not better.
What was added when specs were raised?
WHAT, SPECIFICALLY was added?
What do we need higher specs for? WHAT do you want added, that needs higher specs?
You're just a fucking idiot.
There's no reason why an OS needs to be any larger than it is. Let the market add value to a cornerstone product. There's no reason that the Linux kernel should ever take up a gig of ram because, hey lets throw more boiler plate into it.
Microsoft has one job with Windows, and that's to make the best application shell possible for almost every possible desktop need. I think they've done a pretty good job at it, though they've fucked their UI core so badly time and time again, it feels like they're just re-arranging chairs to justify the upgrade cost.
Bye!
I think it is sad we live in a world where people still aren't shocked by the Vista requirements and want them to be higher. WTF is wrong with the lot of you?
I think this minimum spec idea misses the point. We're talking about an operating system, not an application. The OS should provide a platform (and, to a certain extent, services) upon which users will run the applications that actually get things done. The OS shouldn't have huge minimum specs because it's supposed to be relatively unobtrusive. When we start trying to load the OS down with all kinds of things that ought to be done with apps, we end up with a bloated mess, a one-size-fits-none concept that inconveniences everyone equally. I'd much rather they kept the specs low and pared some of the fluff from the OS instead.
In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
Just to run the OS requires 1GB of ram? ...and I'm meant to be impressed with how "small" this is?
Somebody forgot to tell my Mac that, because more than six years after purchase it's still running the latest OS. I just ran an update this morning, in fact. I think we spent $35 on an upgrade once.
My Mac is no longer supported (hasn't been for a couple of releases) by OS-X because the CPU doesn't do 64-bits. It's not even 10 years old yet, and it isn't supported by OS-X.
.
It was the first Apple computer I bought. It will be the last Apple computer I ever buy.
Apple is a hardware seller. They make money on leaving old hardware behind in their software. Microsoft does not make money on making hardware obsolete, on the contrary, as long as it doesn't take them too long to support something, they make MORE money on supporting old hardware.
Someone on Slashdot is actually complaining that Windows runs well on older hardware? We're through the looking glass here, people.
It's not the OS, but the applications. There is a lot of business software that only exists for Windows and sometimes a very specific version of Windows at that.
16 bit applications were just an example. DOS is pretty much free as is Microsoft's visualization environment if you run 64-bit windows. There still are quite a few legacy 16 bit DOS applications out there, btw. You pay millions of dollars to code a solution back in the 1980's or 1990's and upgrading the software is not always the best option. Heck, there is still a lot of legacy code out there from before the introduction of the MS-DOS PC in the early 80's.
The point is, MS cares a lot about compatibility. A lot of times, "run in XP mode" is good enough to get most problems fixed and 64 bit windows supports compatibility modes going all the way back to the first 32 bit OS, which is Windows 95.
While a program written for Windows 10 probably won't run on Windows 95, a business program written for Windows 95 probably will run on Windows 10, and corporations care a lot about that compatibility.
You're looking at this backwards. The re-training would be an ongoing expense, where Windows is a one time hit. You're investing in a one time Windows expense, that you then make back with interest over the coming months and years by eliminating necessary re-training to be able to use an uncommon and unfamiliar OS.
Re-training is already an ongoing expense with Microsoft products. Office ribbon, Windows 8 tile screen, any slightest change in Windows XYZ where the ABC isn't in the same pixels on the screen or is renamed something intelligible. The biggest drawback isn't the training expense, it's the fear of incompatibility with other companies' software.