Slashdot Mirror


More Looks At Far-Off 'Longhorn'

b17bmbr writes "According to eWeek, the first builds are out, with an SDK. The Register notes: 'Microsoft builds leak regularly, Microsoft knows this, and Microsoft knows that the wider the distribution of the software, the faster it's going to spread all over the internet...The timing is impressive for an alpha build of a product that is not scheduled to hit the streets for another two years, and which could quite easily stretch to three.' Methinks this is just vaporware." And Cleverone writes "Several days before PDC 03' attendees will obtain their copy, screenshots of the new build have already made their way to the net. For those inquisitive few, the build stamp is 6.0.4051.0."

2 of 543 comments (clear)

  1. Quick Version Info by Infernon · · Score: 5, Interesting

    Windows 2000 - Version 5.0
    Windows XP - Version 5.1
    Longhorn - Version 6.0

    So it looks like Longhorn is actually a full version up. Not that I truly understand what any of that means. Anyone have a changelog? :)

    1. Re:Quick Version Info by Jugalator · · Score: 5, Interesting

      I have no idea what is supposed to merit a major version bump in longhorn, though; I guess the new GUI rendering engine?

      No :-)

      Actually, all Windows releases so far with a bump in the major version number *has* been very major indeed. Compare Windows 3.x to Windows 95 with its total change of desktop metaphors, going from icons representing file "links" only to real files, or Windows NT4 to Windows 2000 with enormous changes in the OS core.

      Microsoft may bump a lot of version numbers for their software unnecessary, but I wouldn't say they're doing it with their operating systems. Windows XP only got a 0.1 bump since it is only a revised version of Windows 2000 after all.

      Windows Longhorn will feature radical changes in the GUI, maybe making todays' Windows XP look like Windows 3.11 in comparison. It will also offer code restructures to use the .NET API and attempt to be even more secure than Windows 2003 Server by doing this. All .NET API procedures should for example automatically do basic things like bounds checks, which C++ code seldom does.

      Windows Longhorn will also feature DRM built-in, which might have large implications for the user as well.

      I personally think MS is putting a lot of eggs in one basket with Longhorn. If it's a failure, MS will be hit hard by it, but with the market dominance they have, they're probably sleeping well at night anyway.

      --
      Beware: In C++, your friends can see your privates!