Windows Vista successor scheduled for a H2 2009 release?


Recommended Posts

I want an overhaul of all legacy components:

Yeah me too.

I want BIOS to die or to evolve into something. Also, with RAID controller and a bunch of other on board chips, my pre-OS startup time is much longer than OS-load time. And it doesn't matter how fast the CPU is, it still takes forever to get to the stage when the OS starts to load.

Sadly, there's little MS alone can do to improve on that.

I want an overhaul of all legacy components: remove native support (registry, crazy dlls, etc.) for previous generation apps but allow them to be run using virtualization. That way, it'll be easier to build a componentized (sp?) OS and write programs which function correctly with non-adminstrative rights.

I cannot wait for that day to come :D

if they charge another arm and a leg for it then it'll be a failure no matter how good it is. They should at the very least provide a cheap upgrade option for Vista owners if they're going to release it that soon.

Ohh yeah.

Almost $700 for Ultimate is just way too much.

I want an overhaul of all legacy components: remove native support (registry, crazy dlls, etc.) for previous generation apps but allow them to be run using virtualization. That way, it'll be easier to build a componentized (sp?) OS and write programs which function correctly with non-adminstrative rights.

What's wrong with the registry?

Can you suggest a better alternative for storing settings? I can't.

http://blogs.msdn.com/oldnewthing/archive/...26/6523907.aspx

The registry is simply the best option for saving user and machine settings in a fast, flexible, safe, and secure manner, and It's really the only good way to do component registration.

What's wrong with the registry?

Can you suggest a better alternative for storing settings? I can't.

...

The registry is simply the best option for saving user and machine settings in a fast, flexible, safe, and secure manner, and It's really the only good way to do component registration.

Text files? XML files? Text files work with Linux.
What's wrong with the registry?

Can you suggest a better alternative for storing settings? I can't.

http://blogs.msdn.com/oldnewthing/archive/...26/6523907.aspx

The registry is simply the best option for saving user and machine settings in a fast, flexible, safe, and secure manner, and It's really the only good way to do component registration.

I disagree. The registry is contained in only a few files. Lose any of them and it can be a real heartache getting your system back up. I like the linux way of doing it with text files for different services etc.

I doubt they'll drop legacy code. Same reason Intel won't change their architecture to something that makes more sense. It would take a joint effort including MS, a bunch of major software creators, and a bunch of hardware manufacturers - otherwise it's not worth it to MS to brute force their way through the crap they'll take for making such a drastic change. It would be a terrible financial decision if they did it of their own will with no outside support, even though it is their own OS and despite the fact that they could probably manage it all.

-Spenser

Text files? XML files? Text files work with Linux.

Did you even read the link he posted?

Just a few reasons why those don't work:

  1. It's slow
  2. No per-key security
  3. Not thread safe
  4. Prone to Denial-of-Service attacks (or accidental DoS from badly written apps)
  5. Apps can read/write to them directly, limiting options to extend the format.
  6. Manageability is nearly impossible.

There is no way text files could ever fulfill the purpose of the registry.

But yeah, you go ahead an build COM based up on registrations in a text file. Good luck with that.

I disagree. The registry is contained in only a few files. Lose any of them and it can be a real heartache getting your system back up. I like the linux way of doing it with text files for different services etc.

I'm confused. Aren't two files easier to back up than 200?

Plus, it's not like applications are forced to put settings in the registry. The registry is first and foremost for registration. That is, COM coclasses / interfaces, file associations, handlers, protocols, etc. All stuff that is shared by multiple applications. Putting all that stuff in text or XML files would be a nightmare.

I agree with Brandon. :yes: The registy was/is a nice idea for what it was designed and implemented for. Then come all the developers around the world, and start to store all their programs' settings inside the registry -> of course it becomes big and slow. Then to make things worse, everybody tries to write a registry fixer and optimizer to "speed up your computer by 400%" :angry: . Of course it will become a mess.

I don't know if anybody here knows the story behind the notification area next to the clock. It is the same story :whistle: : it was designed to notify the user about events, then later all the developers had the idea to minimize their application onto the notification area, or create a quickstarter icon there. And now, what do you see there on an average computer: antivirus, firewall, bandwidth monitor, quicktime, nero, adobe, openoffice, nvidia and ati and other tray icons. Was the idea good? Yes. Can you use easily a PC with 15-20 tray icons next to the clock? No.

^^^ Microsoft themselves encouraged software developers to do this. And Microsoft led by example with their apps.

I prefer smaller files, in human-readable (and fixable) text format, that are accessed/read by the system only when needed. System files kept out of user write areas. Per user files kept inside each user's home folder. Clean. Orderly. Maintainable.

Sure, there are benefits to a binary database containing all entries from all apps and the OS. But surely you can see the disadvantages, too. ;)

I hope it's true as well. There may be a lot of annoyed Vista users though.

All Vista users are annoyed already

Even the ones like myself who never have any issues - but dont like the bloated overhead.

Im eagerly awaiting something different - Im getting tired of dual-booting.

Did you even read the link he posted?

Just a few reasons why those don't work:

  1. It's slow
  2. No per-key security
  3. Not thread safe
  4. Prone to Denial-of-Service attacks (or accidental DoS from badly written apps)
  5. Apps can read/write to them directly, limiting options to extend the format.
  6. Manageability is nearly impossible.

There is no way text files could ever fulfill the purpose of the registry.

But yeah, you go ahead an build COM based up on registrations in a text file. Good luck with that.

Why aren't *nix based systems (Linuxn BSD, etc.) a nightmare? Or slow? or less safe than Windows (ha!)? Kudos to them I guess right? Why so many applications do not use the registry and use text or xml or ini files to store settings? And why do many of us have to format Windows and reinstall because the registry (among other things) is full of crap?

Microsoft shouldn't allow people to write to the registry unless they follow proper guidelines.

Well I'd bet we won't see it before H2 2009. But I'm pretty certain Microsoft will make sure it's out before 2011 hits. They said they don't want no more 5 year releases and I agree. But 2 years seems to soon to me. 3 years sounds like a sweet spot, maybe with a better upgrade price too :D

Why aren't *nix based systems (Linuxn BSD, etc.) a nightmare? Or slow? or less safe than Windows (ha!)? Kudos to them I guess right? Why so many applications do not use the registry and use text or xml or ini files to store settings? And why do many of us have to format Windows and reinstall because the registry (among other things) is full of crap?

Microsoft shouldn't allow people to write to the registry unless they follow proper guidelines.

If you bothered to look at the link I posted, it would have spelled in great detail for you the problems posed by these kind of files, and why the registry is "better" than config files in many cases.

Some of the problems are specific to INI files, but a lot of the listed issues are problems that any kind of configuration file can have:

XML manages to sidestep many of the problems that INI files have, but only if you promise only to read from them (and only if everybody agrees to use a standard-conforming parser), and if you don't require security granularity beyond the file level. Once you write to them, then a lot of the INI file problems return.

Mio, some of those issues pointed out by Microsoft to validate Microsoft's direction are specific to Microsoft products only. The very first one talks about the Windows API limitation at the time. The second one poses the "administrator" values versus the "user" values. This would be handled by two different files, as any app with specific settings to work in that corporate environment would be out of reach of the users. And users would have their own settings that are read (local drive or user's 'home' folder off network) so they can make their own preference adjustments (UI settings and such). The third one is purely implementation issue, if two separate tasks are allowed to both open the file in write mode and both attempt writes to it. That's a strawman - it is nonsense, so just don't do it!

Some of the items are true - it takes fractionally longer to read and parse a file that is in ASCII text.

It is just weighing the pros and cons of large binary database versus smaller text files that are only read when needed (and are kept in memory during application run, so aren't constantly re-read and parsed).

I know where I put my money. :)

It would make perfect sense for the new version to come that soon, considering what a huge failure Vista has been.

It's a failure only in the eyes of the AMB trolls, check out CDW's latest report. Doubling OS X's market share in a year is a pretty good indicator.

Now before the fanboys scream "TROLL!", there is not one business I know of switching to Vista, it would be like suicide. The reasons are too numerous to go into now, but it's just not happening. I work in an IT dept and we have been evaluating Vista and found it simply not fit for purpose.

Once again, check out the CDW report, many businesses are now starting their vista migrations, my own employer included.

Windows me was only released 7 months after win2k.

Windows ME was not a successor to 2000 it was a successor to 98, and it was being developed concurrently with 2000 so that feat is not really as impressive as you make it sound.

Yeah me too.

I want BIOS to die or to evolve into something. Also, with RAID controller and a bunch of other on board chips, my pre-OS startup time is much longer than OS-load time. And it doesn't matter how fast the CPU is, it still takes forever to get to the stage when the OS starts to load.

Sadly, there's little MS alone can do to improve on that.

Wait till we get better EFI support from motherboard makers :D

I disagree. The registry is contained in only a few files. Lose any of them and it can be a real heartache getting your system back up. I like the linux way of doing it with text files for different services etc.

Linux is not immune to problems, I have had application installs b0rk in linux that could only be fixed with a complete reinstall.

Why aren't *nix based systems (Linuxn BSD, etc.) a nightmare? Or slow? or less safe than Windows (ha!)? Kudos to them I guess right? Why so many applications do not use the registry and use text or xml or ini files to store settings? And why do many of us have to format Windows and reinstall because the registry (among other things) is full of crap?

Microsoft shouldn't allow people to write to the registry unless they follow proper guidelines.

Not true at all, in fact I personally have found that on every computer I have ever used, applications actually take longer to launch on Linux than on Windows. What the registry gets loaded with is mainly down to vendors writing bad uninstall programs, if you ran windows how it came out of the box, and never installed any applications on it then you would never have to format it, the general rule of thumb is that the fault lies with software vendors.

The actual reality is that the windows registry is rarely if ever used as a vector of attack, it does not make Windows inherently unsafe.

Also, something you folks seem to be failing to consider is that part of the excessive technical complexity of Linux comes down to the way it manages application installs, you have to perform different edits for different apps, whereas with the Windows Registry everything is centralised and editable from a single location, making it much easier to configure and tweak.

Windows ME was not a successor to 2000 it was a successor to 98, and it was being developed concurrently with 2000 so that feat is not really as impressive as you make it sound.

XP was released october 2001. Which is 1? year after win2k, and 1 year after Win ME.

What Microsoft needs to do is start making new OS branches. One that supports legacy, one that gives the whole thing the much needed overhaul.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • This and Crazy Taxi are the two games that interested me the most from this showcase.
    • Good, because the nonstop chattering from the voices in her head made me quit the second game.
    • This new cabinet design lets you run AMD, Intel, and Nvidia PCs inside one case by Sayan Sen At Computex 2026 earlier this month, AMD announced a couple of new X3D processors for both sockets AM4 and AM5 as it confirmed the support extension of the latter till 2029. And although Intel didn't unveil any new desktop chips, the company's Core Ultra 200S Plus series is relatively new too. Let's say though that you want the best of both worlds simultaneously, and instead of running two different systems, you can have both running together side-by-side, or rather on top of one another. That's exactly what Thermaltake's CAPO X dual system is made for doing. While it's not exactly mandatory to run AMD with Intel, or vice versa, you get the idea. As you can see in the render above, it is essentially like a double-decker PC case that is capable of holding two microATX (mATX) motherboards. Even running just one discrete graphics card in a PC can get toasty, so you may be wondering how well the cooling is designed on the CAPO X, Thermaltake has confirmed, as is evident from the marketing promo image above, that the case supports up to two 360 mm AIO liquid coolers. 420mm is not supported. In total there is room for 13 120mm case fans. In terms of I/O (input/output) options for the two systems, there are naturally two places for those ports, one at the top and one at the very bottom of the chassis in the front panel. In terms of use cases, there are many possibilities. Thermaltake itself, for example, highlights how one system can be your main PC while the other could be the AI agent PC. Another example given is how it can be used to stream and game simultaneously with dedicated systems instead of hogging one with the entire load. Nothing regarding pricing or availability was said. Source: Thermaltake (YouTube, X)
    • There might be some passive design improvements (cooling, etc), but I doubt they'd change the core performance spec of the hardware mid-generation when they've already got a new console in development.
    • State of Decay 3 is out in 2027, reveals Plague Nests with new co-op gameplay trailer by Pulasthi Ariyasinghe A few months ago, Undead Labs broke its silence about the third entry in the State of Decay series since its announcement in 2020. Today, the studio had a brand-new trailer to reveal at the Xbox Games Showcase, finally giving players a look at the Unreal Engine 5-powered title. A broad 2027 release window is now attached to State of Decay 3 too. The studio confirmed that every scene seen in the gameplay trailer (except for the studio logo) released today is from the game with no cinematic footage. "The quality bar of the moment-to-moment experience is higher than anything we’ve achieved in Undead Labs’ history," says the studio. "State of Decay 3 is being built in Unreal Engine 5, and we’re creating better quality versions of what makes our game the survival sandbox it is, and the combat experience is really, really important to us, and I think you can see it coming through in this trailer." One new aspect of this upcoming entry is the Plague Nests. These are supposed to be dynamic, dungeon‑like enemy hubs with varied “personas” that change tactics each time one appears on a map. These areas will have the best loot in the game for players brave enough to tackle them. The combat system is being overhauled too, letting players do quick and power attacks depending on the situation. This isn't just on the player's side though, as zombies themselves now have multiple new types of behaviors depending on how fresh or decayed they are. "All of these play very differently, especially as you start getting outnumbered or when you’re making noise and running around and trying to save your rear end or the rear end of your friend next to you," adds the developer. Of course, settlement building and community management are massive parts of this third entry too. These are being further expanded with the cooperative focus, giving players much more freedom for playing together than in State of Decay 2. Players will even be able to split up and build settlements in different areas of the same map with different goals. Undead Labs confirmed that playtests are already ongoing for the title, and interested players can sign up to participate by heading over here once more slots open up ahead of the full release. State of Decay 3 is coming out on PC, Xbox Series X|S, PlayStation 5, and Xbox Game Pass sometime in 2027.
  • Recent Achievements

    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      492
    2. 2
      PsYcHoKiLLa
      247
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      68
    5. 5
      ATLien_0
      67
  • Tell a friend

    Love Neowin? Tell a friend!