As long as the functionality is there and basic improvements have been made, I'm not at all upset. I got my upgrade for free, and I'm enjoying several of the new features (especially multiple desktops, welcome to the 21st century Microsoft).
We've all released minimum viable products before. Hell, "early access" is dominating video games in particular. As long as they continue to improve and have a stable, steady release schedule with tangible results, then I think it was a good move on Microsoft's part. Especially since the longer they waited the more entrenched users of Windows 7 & 8 would become, just like they did with XP.
Windows 10 appears to suffer from the "pick a date" style of project management. A date was chosen before the project started and that's the day it was released regardless of any issues that cropped up in development.
And rolling release is a good model and it seems to be working fantastically for browsers but it's predicated on not releasing features until they are ready. But Windows 10 is a marketed product with features that all had to exist on day 1. So instead of a stable core to work from we get a big ball of muddled together.
I'm hoping now that the date is passed and the features are all in there that there is nothing left to do but fix everything. The (slow) rolling releases of XP worked well so I too have high hopes for Windows 10. But I'll be waiting for a while before I upgrade.
Comments
As long as the functionality is there and basic improvements have been made, I'm not at all upset. I got my upgrade for free, and I'm enjoying several of the new features (especially multiple desktops, welcome to the 21st century Microsoft).
We've all released minimum viable products before. Hell, "early access" is dominating video games in particular. As long as they continue to improve and have a stable, steady release schedule with tangible results, then I think it was a good move on Microsoft's part. Especially since the longer they waited the more entrenched users of Windows 7 & 8 would become, just like they did with XP.
Windows 10 appears to suffer from the "pick a date" style of project management. A date was chosen before the project started and that's the day it was released regardless of any issues that cropped up in development.
And rolling release is a good model and it seems to be working fantastically for browsers but it's predicated on not releasing features until they are ready. But Windows 10 is a marketed product with features that all had to exist on day 1. So instead of a stable core to work from we get a big ball of muddled together.
I'm hoping now that the date is passed and the features are all in there that there is nothing left to do but fix everything. The (slow) rolling releases of XP worked well so I too have high hopes for Windows 10. But I'll be waiting for a while before I upgrade.
I disagree. Basic UI issues are not excusable for a company with the resources of Microsoft.
If we were talking about issues in a brand new kernel, maybe. But not basic UI issues.
Why are _kernel_ issues excusable but UI issues are not? I think you have that backwards.
Bugs in massive undertakings like a kernel are unavoidable. It's a bitter pill to get a big improvement.
Using the wrong UI framework for dialogs or having links going nowhere is easily avoidable, it just needs manpower.
Actually, it's not excusable to have issues in the kernel or UI.
I just brought up the kernel thing because I was pandering to someone inventing poor excuses for MS. I shouldn't have pandered.