Vista was not a very well-received release, but I remember using 64-bit Vista way back when. Maybe my memory is failing me a little, but I don't really recall Vista being that bad or unstable. UAC, of course, was a little annoying then, but 7 felt a little more unstable and crash-prone than Vista.
My dad still uses a Vista desktop regularly (a 2007 install) and as far as I can tell it still works perfectly fine for him. I suppose he's probably leaving far too much to chance, but still.
Aside from UAC... the biggest issue with Vista is that the required system resources was a significant jump over XP, and too many manufacturers shipped machines that were simply too under-powered for the preinstalled OS.
In those days, I remember seeing Vista laptops with 1 GB of RAM, on which Vista was unusable. People had to edit arcane registry settings to disable the "Aero" look-and-feel, and drop down to a more Windows 95-like display just to run at all.
It really was basically fraud, and infuriated everybody. If Microsoft had been more realistic about their "certified for Vista" specs, it probably wouldn't have been such a flop. On the other hand, new laptops jumping from 1 GB of RAM to 4 GB minimum overnight would have been a hard consumer sell, I suppose.
IIRC among other pressures, Intel pushed Microsoft to consider one of their weaker GPUs Aero compatible. That allowed many PC OEMs to ship Vista PCs with very underpowered GPUs.
The weakest Intel GPU that can support Aero was the Intel 945G. There is also the 915G that don't have a WDDM driver, which is even more of a problem now given that they ditched XPDM support in Win8.
UAC was not that big of a deal. I used Vista and it hardly bothered me. I suspect most of the whining came from people not used to the separation of user and administrative privileges.
This also reminds me of how the DRAM manufacturers tried to do the 1Gbit DDR2 crossover during 2007/2008, when 64-bit Windows was not common until mid-2008. Needless to say it was a serious mistake (I think Qimonda went into bankruptcy during that time). Even on laptops, DDR2 used BGA not TSOP.
Vista was the first Windows release I really felt was unsuitable for installing on most systems which were purchased before the OS was released. OEMs made the problem worse by pre-installing it on low-to-mid-range systems which had no business running it. Additionally, if you were running 64-bit Vista at release, there were significantly more driver issues than with the 32-bit version, though running the 32-bit version meant you could barely support enough RAM to let the system start performing well.
UAC issues cleared up once all of the software developers got around to releasing the next versions of their applications, but MS took most of the blame. I can't really blame the developers for not wanting to make significant changes to their software before the final release of Vista, given the chain of events leading from XP to Vista. Many are already hard pressed to remember how rocky the XP release was, and that MS did much more in XP to make 3rd party applications work with the system. In Vista they essentially took the extra step to warn the user that the application was misbehaving, rather than silently letting it happen. Some people got into the habit of disabling UAC by default and I had to convince one person who should have known better that he wasn't going to suffer from a deluge of support calls if he stopped disabling it in Windows 7 (and the handful of Vista systems still around).
In the end, 7 put very little in terms of functionality or stability on top of Vista SP1, though Microsoft did put significant work into making it possible to run 7 on systems that didn't have the horsepower for Vista. The marketing push brought a lot of people around. I look at it as an essential part of the strategy they're currently using with Windows 10 (vs. 8), though they took the extra step of changing the underlying version number this time around (something they didn't do when going from Vista to 7).
The biggest problems with continuing to run Vista are that the support window is rapidly closing and 7 will usually perform better on the same hardware (because they toned down the UI and put real effort into getting 7 to work on hardware that was previously running XP).
1. Vista disabled parallel ports direct access, new cnc machines, or people using old printers and scanners still use xp.
2. Vista removed support for directx before dx10... Microsoft realized later how shitty idea that was, but instead added dx9 and below emulation layer. The problem is that it only works almost 100% right on win 7, thus why many gamers still use it ( instead of 8+ where some good games are very buggy or slow )
3. Vista audio model disallowed drivers to do anything that could be used to disable hdmi drm. As side effect all 3d sound cards stopped working properly. Lots of people blamed Creative and other sound card makers, that got generally screwed... now that this tech proved to be essential for vr gpu companies are doing workarounds, for example AMD has as selling point of TruAudio that it skips Windows normal audio stack.
Also wasn't that the release that had endless popup warnings asking permission for arcane things. Anyone who used it became trained to just click "Allow" a dozen times just to get on with what they wanted to do.
The issue was chiefly that XP didn't enforce good programming practices (storing user info in /Program Files/ was rife and one of many issues). Introducing the UAC security structure meant that suddenly all of these applications tried to do things that triggered UAC elevation prompts.
This was addressed twofold, as far as I understand: 1) Application developers were railroaded into best practices and forced not to do terrible design ideas, and 2) MS introduced a whole load of compatibility features such as virtualising folders transparently so when bad apps still tried to do bad things, it was securely captured and diverted around requiring a UAC elevation prompt.
Regarding the stability issues, Vista's driver model was new when compared to XP. Naturally, the number of bugs in drivers increased initially but slowly settled down. Much of the '7 is more stable / faster than Vista' groupthink is the result of bad drivers getting better in the intervening years.
Lots of changes to things that broke a lot of existing applications and drivers and I don't know if it was software shops just dragging their feet or MS not giving them enough time to update their software but it was pretty messy for the first year or so.
In the first few paragraphs of the article it mentions
> The project, however, failed completely and development had to reset. More than three years late Microsoft released Windows Code Name 'Longhorn' as Windows Vista.
> Did you even read the first few paragraphs of the page?
I did. I also worked at Microsoft during the years in question.
edit in response to your edit: The project was restarted. Longhorn and its three pillars were essentially thrown out. Windows Vista was rebuilt from scratch on top of Windows Server 2003. I assume they chose to keep the same codename so as to reduce confusion. But that doesn't mean it was the same OS.
> Please don't insinuate that someone hasn't read an article. "Did you even read the article? It mentions that" can be shortened to "The article mentions that."
Yes. The website we're looking at refers to Longhorn, a defunct operating system project that was canceled by Microsoft and replaced by a new project with an identical codename.
Vista 64 was preinstalled on the family computer (HP Pavilion m9458fr bought in july 2009 for 416€ on eBay hp_marketplace_fr). I have installed linux on a second partition like for my previous computers, but on my previous computers, I was using windows 99% of the time. With Vista 64, I have been unable to find drivers for my expensive scanner, nor for my printer. This was so much annoyance that we (my wife and me) were using linux more often than windows.
After a couple of months, we made the complete switch (deinstall the email client on windows and create more gmail accounts).
Now, I boot on windows less than once per year. I have to thank the driver problems of vista 64 (and the other minor defects of Vista 64) for making this migration possible (it is difficult to leave a system we are used to).
My only problem now is that I would like to buy a new computer and I am worried about the full support of all my future hardware.
In the last few years, we've started purchasing Dells with Ubuntu pre-installed. Most of them get imaged with Windows 10, but the machines which stay in IT and a small number of faculty members teaching IT-related courses usually get configured to dual-boot.
I have been using Virtualbox to deal with everything I need to do in Windows rather than going through the hassle of rebooting the machine. I use Windows for Active Directory administration, the occasional document that doesn't look right in LibreOffice, and occasionally jumping into Adobe software. My next computer at work is going to be a MacBook Pro with a Windows 10 VM, but at that point I should have most of the Adobe and MS Office tasks covered in OS X instead of the VM.
It'd be great to work so fluidly between machines. I get a headache switching back and forth between desktops like that - its kills the flow to stop and struggle with finding a setting or even a close button when its not where I automatically reach for.
As for VirtualBox, strange but I just yesterday spent 2 hours trying my best to use it and failing. It just wouldn't resize the window beyond some tiny vga thing. None of the online help did squat; none of the menus and settings had any affect. So I finally gave up. That thing has a ways to go before its useful for a desktop environment.
Vista OEM installs were quite optimized. My Dell XPS laptop from 2008 used to run Vista very smoothly. However my friend installed Vista on a desktop with similar config but with AMD processor and the performance was pretty bad.
My dad still uses a Vista desktop regularly (a 2007 install) and as far as I can tell it still works perfectly fine for him. I suppose he's probably leaving far too much to chance, but still.