Microsoft Windows 7 "Wishlist" Leaked
Cassius Corodes is one of many readers to point out that a recent "wishlist" of new Windows development features is floating around the net. This list was supposedly leaked from Microsoft and contains some of their key development features for the next version of Windows. Given that the next new Windows release is bound to be a long way off I would recommend seasoning this news with a hefty dose of sodium chloride.
Back up XBOX 360 games to Windows PC - Ain't gonna happen
New PIP functionality for Media Center - PIP *.WMA/L
Infinite desktop, virtual desktop idea - Maybe they could port fvwm
Option to "Reopen Closed tabs" in IE - This will be addressed via "Are you sure you want to close this tab?"
Auto clean of Temp folders - How about including a way to define which are temp folders.
How about fixing the paging to use it's own partition, ffs!
A feeling of having made the same mistake before: Deja Foobar
So is this a new list or did they simply take the list of all the features they removed from Longhorn before it became Vista and exchanged the header?
Assorted stuff I do sometimes: Lemuria.org
7 Things for Windows 7
No DRM
No Bloat
No Eye Candy
No ClearType
No Authentication or WGA
No Restrictions for Video or Audio Output
No Search Indexing
Yup, I still remember when I got all excited about the WinFS Filesystem (yeah, in the ATM Machine) which was supposed to come in Vista... this "leak" was surely "leaked" by Microsoft's hype department.
Ubuntu is an African word meaning 'I can't configure Debian'
While we're at "sensible default settings": Show those damn extensions!
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
Really, after Windows Vista i have really just stopped caring about what MS does. They can do whatever but i doubt Windows 7 will be anything but some minor enhanchements and some new fancy clothes when the day for gold comes. If they horribly failed with current codebase how can they do any better without a major rewrite in just a couple of years? It must suck for MS to have put themselves in this position.
HTTP/1.1 400
I began noticing this with Windows 95. The bastards said it would run in 4MB of memory. Technically it would, if you only ever wanted to start it up. (12MB was the bare minimum to run some modest apps without paging.) I admined a Dec PDP 11/45 and learned a lot about tuning a system for performance. When you had 256 KB of memory, 2 88MB HDDs, a 4 MB core memory swap disk (anyone ever see a Megastore? :) and had to shared nicely among as many as 40 users at a time, you learned how to get the most out of it. Seems the approach these days is: Throw more money at it. Buy more RAM, bigger HDD, upgrade (why do Windows upgrades always require tonnes more RAM?), faster CPU, etc. Performance tuning at Microsoft seems blasphemy.
A feeling of having made the same mistake before: Deja Foobar
It should also have a companion option "Fill my notification area with lots of little static icons for programs I seldom use, but to the developers they were the most important thing in the world so they want them to be already started on the rare occasions I might want to use them, least I judge the developer by the 5 second delay of starting their program, on startup."
The companies' logic is that programmer cost a lot. It's actually much cheaper, they think, to throw some money in buying more hardware to make up for the lack of optimisations in the code, than to waster the precious ( = expensive in terms of salary ) programmer's time.
Where this is actually true remains to be seen.
Specially given the current trends in hardware (additional power doesn't come from more raw power but from additional parallelism, etc.) the programmers will have *anyway* to be clever, because better hardware won't be able anymore run the same shitty code faster.
As Herb Sutter puts it The Free Lunch is Over.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
"Performance tuning at Microsoft seems blasphemy."
Actually maximizing performance means that you're not buying new hardware, which pisses off Microsoft's OEM partners. And in turn, that means you're not buying new copies of Windows as well.
Earlier this decade, even the cheapest PC you could buy off the shelf had far more horsepower than was necessary for apps of the time. With the sole exception of video cards, any El Cheapo Celeron you could buy would easily exceed the hardware standards for the latest games and apps. PC sales slowed down. The solution? Design apps and OS's that have so many bells and whistles that they use up all that excess computing power, and Voila, you have to buy new hardware.
Performance tuning? Are you kidding?
Life is hard, and the world is cruel
While were on the subject of poking in the registry, how about making the registry a file system that is mounted and can be checked for errors? Or at least some kind of format that isn't obfuscated. Make it a real database or something.
For exactly the same reason we can't just run all our apps under Wine, or switch to another OS entirely: We use Windows for its cruft. Developers write some strange code due to poor programming skills, unreasonable deadlines, or simply because it was easier to hack together a workaround than trying to get Microsoft to fix a buggy library or API. Then Microsoft decides to update Windows, and does their best to make the new OS run all the horrible code that somehow managed to work on the old OS... Which just makes the new OS even cruftier and buggier than the last. Repeat this cycle a dozen times and you have Windows Vista.
Unfortunately, even though Microsoft's coders would love to start from scratch, and I'm sure they could put out a good OS if they wanted to, Microsoft knows we use Windows for its cruft. If Microsoft suddenly cut old legacy apps loose (or confined them to a Classic-like abstraction layer) the new Windows would lose its main advantage over *nix or MacOS. Microsoft doesn't want to compete on features, or ease of use, or really compete at all, not when it's so much easier to beat the market over the head with their Club of +1 Legacy Support.
Our only escape from this cycle is, as customers, to do our best to rid ourselves of unmaintained, poorly written, legacy apps. Make the case for open source, virtualized, web-based, or any high-agility solution that won't tie you to some arcane software or hardware down the line. Microsoft will only rethink their strategy when the market for cruft begins to die out, so do your part.
How can I believe you when you tell me what I don't want to hear?