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."

20 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: 3, Interesting

      There might be a lot of "under the surface" changes in Longhorn, making Microsoft think it's worth increasing the major version number. I think parts of the OS will be rewritten to use .NET API's using managed code (i.e. more secure code with better bounds checking, etc). They'll introduce the new file system WinFS that's implemented as a layer on top of NTFS and will make working with the files on a system more like working with a database. Whatever that will mean in practice might be unknown at this point. :-) They might also introduce DRM as part of the OS, which could have all sorts of implications to the user.

      So there's a lot of known and unknown features planned, and since I haven't tried a Longhorn Alpha, I don't even know exactly what's in it so far. There are of course all sorts of visual changes, and the PDC build have already revealed dozens of surprise changes like an improved Internet Explorer with for example anti-popup support, a new plugin architecture, and a new download manager, etc.

      Since Windows has a lot of software integrated, it's hard to keep track of all changes, especially if you're going to do it in detail, this early. Longhorn isn't even in Beta yet.

      --
      Beware: In C++, your friends can see your privates!
    2. 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!
    3. Re:Quick Version Info by bmajik · · Score: 4, Interesting

      1) i'm not touching that at all :)

      1a) irregardless isn't a word :)
      ok, i'll bite a little. I have a hard time beleiving that everything in linux is a 100% clean room implementation, when the point of linux and the GNU toolchain was to make a freeware clone of UNIX. So, im predisposed to thinking there's some lifted code or designs in linux. On the issue of who that was lifted from (was it sco ?) or if that actually matters (there are only so many ways to write a VFS layer, or grep) i don't really have an opinion, and im not really qualified to have one. in general i think our society is too litigous and there are lots of frivilous lawsuits. On the other hand, the open source phenomenon presents a big challenge for commmercial software vendors in the following sense: according to the Fredrick Brooks classic "the mythical man month", dev time is 1/6th of the wall-clock time in a software engineering effort. The rest comes from design and testing.

      Alot of what's happening in the linux space is wholesale cloning of existing software/features, with careful picking and choosing of whats great and what sucks about the peice being cloned. The design is apparent in the functionality of the system to be cloned - so thats time and expense that some proprietary company went through that the linux project is avoiding (potentially). The "testing effort" is simply "does it work as good as the original?" so significant time is saved there as well. In effect, the linux clone/improve effort can clone functionality faster than it can be created originally in many cases, and of course free software has the "side effect" of pulling the market out of commercial software if it truly is an acceptible feature parity clone of the commercial offerings.

      So i think part of what SCO is doing is reactionary - they're saying "this can't keep happening - these people are cloning our designs, cloning our interfaces, and we think they're just flat out stealing code in some cases. then they give it away for free and we of course suffer as a result"

      i think this is a hard problem that really comes down to wether or not you think intellectual property is a real thing or not. the classic problem with IP is the following:

      company X spends 10b over 20 years to develop a drug that effectively treats a human ailment. Once discovered, manufacture of this drug is essentially zero cost per part. The 10b research cost has to be amortized over a certain volume of pills for a reasonable time period to allow return on investment, otherwise the company goes under and brilliant people dont figure out new ways to cure ailments.

      at the same time, the drug is just a molecule and may even be easy to produce in your kitchen. why can company X stop you from mixing water, baking soda, and maybe 3 other things in your own home ? what about if you sell your concoction more cheaply than they do ? should they be allowed to stop you ?

      Now to throw in a twist - what if company X's molecule is too expensive to buy in 3rd world countries, but those people need this medicine as well?

      precisely the same problem exists in software. Someone does all the hard work, then its cloned cheaply by others, and given away for free, typically because people want to
      1) do it themselves
      or
      2) are in developing countries and cant afford US prices for things

      (we see lots of linux adoption in developing countries, actually)

      anyway, back to the specific SCO issue:
      the biggest thing that irritates me is that most slashdot posters beleive 110% that the whole case is completely BS and that SCO is making a frivolous lawsuit. i think there may be something to their case (see above - i have a hard time beleive linux is 100% clean room), but i also don't know what SCO is hoping to get out of all of this.. the cat is out of the bag, so to speak.. linux and other free unixes are "good enough" for many problems.. at least as good as SCO probably ever was.

      2) i

      --
      My opinions are my own, and do not necessarily represent those of my employer.
  2. mem usage by Anonymous Coward · · Score: 1, Interesting

    does this use more or less memory than win2k, winxp?

    any benchmarks yet? (Yes I know the OS is only a quarter baked)

  3. Re:Where Could They Possibly Be Getting Their Idea by stubear · · Score: 2, Interesting

    Do you see any anisotrophic highlights in the grey window border elements? No? Then it wouldn't be brushed metal, it would be a grey gradient now wouldn't it? Besides, this is an interim UI for the alpha and quite likely the beta. The final UI, much like with XP won't be introduced until the OS is well on its way and close to release.

  4. IE changes by Jayde+Stargunner · · Score: 4, Interesting

    Noticed in some of the screens that the Longhorn IE has both a pop-up blocker/manager as well as a download manager (ala GetRight).. Kinda interesting developments--although I suppose we'll have to buy Longhorn to get that version of IE. Heh.

    -Jayde

    --
    What's a sig?
  5. Free beta (um, alpha) testing! by Knights+who+say+'INT · · Score: 2, Interesting

    It's a smart move, after all. Instead of releasing a late alpha version as a product (like Win95) that'll have to be endlessly patched and fixed and improved (Win95 Plus, Win98, Win98SE), they're quietly leaking alpha versions so people can report bugs and they can fix it over two years until they have a 98SE-like stable build to market.

    Well, it's a smart conspiracy theory.

  6. Re:Karma to burn... by Tim+C · · Score: 2, Interesting

    You remind of CNN for technology. Unbiased "News". feh.

    You must be new around here (checks uid - ah yes, 6 figures).

    Slashdot has never been about unbiased news in all the time I've been here; it has always had a heavy OSS bias, and especially for Linux. That's not necessarily a bad thing, although I'd argue that it's not necessarily a good thing, either

    If you want completely unbiased tech news, you're in the wrong place. On the other hand, your attempt to draw parallels between MS "leaking" betas and Linux test releases is non-sensical. The former is not meant for general release, while the latter most certainly is, at least for those willing to risk using potentially unproven code on their system.

  7. Re:Uh... by op00to · · Score: 2, Interesting

    Damnit, and here I was thinking he was wrong....

    [from the jargon file]

    vaporware /vay'pr-weir/ Products announced far in advance of
    any release (which may or may not actually take place). The
    term came from Atari users and was later applied by
    Infoworld to Microsoft's continuous lying about Microsoft
    Windows.

    See also brochureware.

  8. Re:Hype?? by insertionPoint · · Score: 2, Interesting

    What hype? Hardly anybody outside the tech world and non-geeks have any clue about what Longhorn is or really care.

    Accountants and other non-tech users are being targeted with all sorts of interesting press releases etc... You didn't get any? I think that is because slowly the tech world is turning not against Microsoft but towards the idea that alternatives exist. I am betting that when Foghorn Leghorn (or whatever) is released the non-techies will be tripping over each other to get their companies 'standardized' on it. Then techies will be faced with enormous resistance to any resistance about adapting it.

  9. Re:How do you assume this? Thats 2007. by Anonymous Coward · · Score: 1, Interesting

    At the current rate Linux will have competitive marketshare to Windows within a few years.

    I was hearing this in 98-99. It wasn't true then and it isn't true now. Microsoft is a moving target for linux and every update and bugfix removes more of the complaints ppl have about windows and removes incentive to change. Linux's success counts on MS failure and MS is getting better.

  10. Re: biggest flop since ME by LaissezFaire · · Score: 2, Interesting
    Windows ME was a strange release for Microsoft. I believe most of the reason it was a big flop was that Win2k already had most of the home use (e.g. Direct X, plug and play, USB) features built in.

    Almost everything I wanted to run from Windows 95 ran on Windows 2000. The stuff that didn't looked like it explicitly asked the OS what it was, and since the answer was "NT", decided that Direct X wouldn't work.

    Also, since the Windows 95 line was officially dead, and MS has been putting out for years that they would merge the codebases / features, paying for an ME upgrade was silly.

    Longhorn is a continuation of the NT codebase and the NT product. It should be much more straightforward for Microsoft to push people to Longhorn than encourage folks to buy ME.

  11. They have some good ideas by Jameth · · Score: 2, Interesting

    Two or three, at least.

    The best one is letting windows work with their title-bar a bit more. Note that, in the screenshots, explorer has the page title in larger text, a go-to location button, and a location bar all in the title bar of the window. Not that it looks excellent in that case, but there are many cases where it is nice to be able to work with the decorations a bit more. Most things that want a custom top right now just hide decorations, but they look to still be using the same theme on that title-bar as on the rest of the desktop.

    Also, during the installation they look to have explanatory help, something most Linux distributions might want to do better on.

    I'm sure there was a third good idea I noted, but it's really hard to see. Basically, it's still just a dressed-up version of WindowsXP. I suspect they are still working more on the internals, as they don't really want to design all the GUI crap until they know how much they can do with the internals, such as the Kernel and the FileSystem (especially the FileSystem).

  12. Re:They put themselves in that spot. by Crashmarik · · Score: 2, Interesting

    I really hate to explain myself, but you raise significant points and point out misperceptions. Saying microsoft is not competetive is so completely laughable its funnier than the addams family episode I am watching. Microsoft is the default choice. Its Coke and Pepsi. Everything else barely amounts to RC Cola. They are in a bad place because they have allowed their competitors an opportunity to increase their market share at microsofts expense, and they seem to have mismanaged their product cycle.

    OSS does have the same problems anyone else does when they add features to a system. Sorry to burst your bubble on this but new features break old code. When this happens both OSS and Closed source incur the same penalty of upgrading and adjusting system configs. In the case of OSS there is just the cost of labor. In the case of closed source their is a labor cost and there is an ass making you pay full tarrif for what you own 99 percent of.

    Its not a question of things going away. It is a question of things not working the same way. If you want features that have been dropped please just check the man pages for the word deprecated.

    I have gotten office 97 to work on XP. Its no more unpleasant than finding out that the Telnet daemon is not installed by default in redhat and having to get that running.

    Free software is nothing mystical. Open source is meerly an improved process of developing software. The comparison between closed source development and open source development is much like the change in mathematics before and after algebraic notation was developed. The mathematics is the same, the results are the same it just became alot easier to read and make contribution. The same is true of open source. The same principles govern, the same results are obtained, its just much easier to see whats going on and to make a contribution.

  13. Re:How do you assume this? Thats 2007. by ealar+dlanvuli · · Score: 3, Interesting

    I'm at a hospital that intends to move 3000 machines to "some alternative" (basically the options at the moment are linux and linux) inside the next 5 years.

    We intend to replace a great deal of our server room as well.

    The people who communicate with us will need to support our formats, people with larger contracts will be told to ditch Excel.

    This particular hospital used to have a MS site license for Windows + Office on every machine here. It's only a matter of time before even more places do this.

    Also, I've seen three companies switch to be mostly Mac based in the past year.

    --
    I live in a giant bucket.
  14. Re:How do you assume this? Thats 2007. by AKnightCowboy · · Score: 2, Interesting
    I'm at a hospital that intends to move 3000 machines to "some alternative" (basically the options at the moment are linux and linux) inside the next 5 years.

    That's all well and good, but within the same time frame there will be 300,000 new computer users who will experience Windows as their first OS. I'm sorry, but Linux has never, is not, and will never be a mainstream operating system. I would love to see it as much as the next guy, but it's just a hacked up UNIX-like OS built by a bunch of volunteers. Most people do NOT care about the free-software ideology, they just want to turn on their computer, read their e-mail, browse the web, and look at porn/pictures of their grandkids (not necessarily the same people). Why screw around with Linux when Windows comes for free on their computer?

  15. Re:Finally!!!! by smittyoneeach · · Score: 2, Interesting
    Oh, you mean like this example supplied with my Visual Studio Enterprise Architect?
    C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\samples\winui
    \Shell\Fakemen u>nmake

    Microsoft (R) Program Maintenance Utility Version 7.10.3077
    Copyright (C) Microsoft Corporation. All rights reserved.

    cl -c -DCRTAPI1=_cdecl -DCRTAPI2=_cdecl -nologo -D_X86_=1 -DWIN32 -D_WI
    N32 -W3 -D_WINNT -D_WIN32_WINNT=0x0500 -D_WIN32_IE=0x0500 -DWINVER=0x0500 -MLd
    -Zi -Od -DDEBUG FakeMenu.c
    FakeMenu.c
    Rc /r -DWIN32 -D_WIN32 -DWINVER=0x0500 -DDEBUG -D_DEBUG FakeMenu.rc
    link /DEBUG:full /DEBUGTYPE:cv /INCREMENTAL:NO /NOLOGO -subsystem:windo
    ws,5.0 -out:FakeMenu.exe FakeMenu.obj FakeMenu.res kernel32.lib ws2_32.lib msws
    ock.lib advapi32.lib user32.lib gdi32.lib comdlg32.lib winspool.lib
    LINK : fatal error LNK1181: cannot open input file 'link.obj'
    NMAKE : fatal error U1077: 'link' : return code '0x49d'
    Stop.

    That 1181 error, and its cousin, 1104, are less than well documented, let us say.
    I thought it was my project that was having issues, as I randomly tried crap to make it go, both in the dialogue-maze of the IDE and hacking the .rsp file (kudos for the .html build log--I haven't seen a more aesthetically pleasing example of stuff not working in some time) and invoking link.exe at the command line.
    I don't know: this is a stock install, and I used the Visual Sudio .Net 2003 command prompt, which invokes vsvars32.bat, so I'm guessing that the likelihood of Operator Error is kinda low in this case.
    But enough of this ranting. It is time to reboot and load a reasonable development OS, because I lack time to dick around with stuff that should "Just Work." , to mooch your phrase, sir.
    --
    Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
  16. Re:Then you're mistaken. by bmajik · · Score: 2, Interesting

    ok. so let me clarify. I'm not saying that developers make all decisions about MS product design - far from it. however, someone who's title is "marketing", or "sales", or is in the sales/marketing organization is not making product decisions (although they do make valuable suggestions/feature requests, as they're the front lines in dealing with real-life customers)

    the PM will solict feedback from various sources and that drives what does and doesn't go into the product. It may very well be that the target "market" of a product is a novice, and thus the settings would be all wrong for someone who was a power user. That is not a decision made by a "marketing" person - that is a PM decision, based on feedback/research/whatever that the PM has put together.

    i dont work on the office team, so i cant tell you who the word experts are or aren't, so i dont want to argue about stuff you've heard vs stuff i've heard :)

    re: ui guidelines:

    do you think marketing people have access to dropoff .jpg files into the build servers ? or, in the case of Win32 controls - do you think that the title bars in windows are just GIFs that get scaled ? They're programmatically drawn - marketing people aren't checking in code changes to the windows sources!! The security on the windows source code from even a read-only perspective is so tight (following some publicized breakins a while back) that there is no chance that someone in the sales/marketing org could change some content even if they wanted to or knew how..

    --
    My opinions are my own, and do not necessarily represent those of my employer.
  17. Opinion rooted in ignorance by t0ny · · Score: 2, Interesting
    Methinks this is just vaporware

    There is a reason builds leak out of Redmond- its because, when they are creating a new build, the development team is using it internally. So when you say they are making a version of Windows which isnt really working, you really dont know what you are talking about.

    There was a series of articles linked here about six months ago which detailed the processes they use to create and test Windows. It was very impressive, and very professional. After seeing that, I have no doubts about the future of Windows being bright.

    Feel free to mod me down for saying something all the MS-haters dont want to hear.

    --

    Manipulate the moderator system! Mod someone as "overrated" today.