Slashdot Mirror


The Microsoft Singularity

jose parinas writes ""Microsoft Research has published the first details of a wholly new operating system under development called Singularity, designed new from the ground up, built on a new language and designed with emphasis on dependability instead of performance.""

615 comments

  1. Papers? by conJunk · · Score: 0, Troll

    did anyone check out the "papers" section? while i'll certainly try to keep an open mind and judge the final project on its merits, it's hard to take something seriously when its website is gussied-up with a bunch of papers, pretending to lend an air of accademic support for this project

    all those papers were either given at microsoft headquarts, or the HotOS conference, which was an invitation-only do sponosored by Microsoft's reasearch department.

    i really want to be open minded. microsoft *has* been responsible for some real innovation, and *does* have a few products that work really well. hell, singularity might even be cool. i just get a little doubtful, and certainly turned off, when i see that it's leaning on a pile of pseudo-academic support for credibility.

    1. Re:Papers? by Anonymous Coward · · Score: 5, Informative

      For what it's worth, HotOS is an actual respected academic workshop. It was sponsored by Microsoft, but then again, Microsoft sponsors lots of real, respected academic conferences.

      The Singularity project is run by top-notch researchers with very good reputations in the academic community. This is the real deal.

      I think Slashdot has an acronym for things like the parent post... FUD, was it?

    2. Re:Papers? by Anonymous Coward · · Score: 0

      this is common practice within a company to publish internal whitepapers describing the design criteria for a new product. They aren't supposed to be peer reviewed science journals or something like that.

    3. Re:Papers? by Kupek · · Score: 4, Insightful

      I don't understand your complaint. They wrote some papers about their research project, why wouldn't they put them on their site? Before you dismiss the quality of the papers, you want to actually read them.

    4. Re:Papers? by Anonymous Coward · · Score: 2, Interesting

      I wouldn't call it FUD. Considering all the "independent" OS studies MS puts out, not to mention the outright lies their marketing department (or marketing firms hired by them) passes off, I think MS has very little credibility when it comes to announcements that aren't backed by much substantial. I don't doubt they have very good people doing very good research, but the company as a whole has no credible marketing capital.

    5. Re:Papers? by Anonymous Coward · · Score: 0

      "It was sponsored by Microsoft, but then again"

      No. It was not that it was sponsored by Microsoft; it is that it was sponsored almost to its enterity by Microsoft and it was "invitation only", where invitations could come only from... Microsoft.

      "I think Slashdot has an acronym for things like the parent post... FUD, was it?"

      Well, you are the one trying to convince us that it is just the same an open workshop sponsored by, say, Microsoft... AND Oracle, AND Cisco AND Red Hat than a closed workshop sponsored only by Microsoft. That's not called FUD but, anyway, its name doesn't look pretty either.

    6. Re:Papers? by joschm0 · · Score: 3, Funny
      I dare you to name one.

      Well let's see, there was Bob. Now that was real innovation.

      --
      01/20/09
    7. Re:Papers? by shadowmatter · · Score: 4, Informative

      Also it's worth noting that, first, HotOS isn't "invite only." That's why there is a call for papers on the web site referenced by the grandparent. Second, the review is double blind, so there's no chance of papers submitted by Microsoft Research getting special treatment by the reviewers. So I'm not really sure what the grandparent is alluding to.

      MSR isn't the first research group to think of using new language constructs to enforce security. Check out this paper on Asbestos, appearing at SOSP, for something similar. But one thing is certain: MSR has a large pool of talent and the money to push this research endeavor farther than any other company or academic institution could, and that is something exciting.

      - shadowmatter

    8. Re:Papers? by Kupek · · Score: 2, Informative

      No. It was not that it was sponsored by Microsoft; it is that it was sponsored almost to its enterity by Microsoft and it was "invitation only", where invitations could come only from... Microsoft.

      False. "Sponsored" by Microsoft means they donated money to it. It's a USENIX sponsored conference (which, if you're not aware, is an organization that sponsors highly respected systems conferences). It does not mean that Microsoft ran the show. Out of a 12 person committee, only two are from Microsoft Research.

    9. Re:Papers? by Anonymous Coward · · Score: 0

      Do you even know what you're talking about?

      If you need more evidence that HotOS is real, look at the list of papers and the people who submitted them. This is a "who's who" of operating systems research. Need more evidence? Look at the Call for Papers, which lists the program committee. Same thing. If you read through the conference proceedings for other top-notch conferences like SOSP and OSDI, you'll see all the same names.

      HotOS is invitation only because the whole idea of a workshop is to have a small group that can have real discussions about their research. Invitees are NOT selected by Microsoft; for the most part, they are given to the people whose papers were accepted, so that they can show up and discuss their work. Microsoft provided some financial support for the conference, but they are NOT the ones running the show.

    10. Re:Papers? by Anonymous Coward · · Score: 1, Insightful

      Posting as AC, so I don't care who reads this, I just wanted to get this off my chest.

      I have wondered what would ahppen if Microsoft sent a team of developers off to build a new operating system from the ground up. Regardless of what people think, they have some of the worlds best developers. Now, they've gone and done it. I can imagine Micsrosoft having the best operating system out there, under those circumstances. They could just end up winning, after all.

    11. Re:Papers? by Anonymous Coward · · Score: 0

      Is that you, Ballmer?

    12. Re:Papers? by GileadGreene · · Score: 5, Insightful
      Please keep in mind that MS Research is quite a different beast than the production departments of MS. MS Research does a lot of respected work. They also employ some of the most reputable researchers in software and OS development, including:

      I dislike MS production software and business practices as much as the next guy. But don't make the mistake of underestimating MS Research just because you dislike MS.

    13. Re:Papers? by Mistshadow2k4 · · Score: 1

      So it's not just another MS project. That's interesting. But who will own the copyright to it when it's finished?

      --
      I dream of a better world... one in which chickens can cross roads without their motives being questioned.
    14. Re:Papers? by lgw · · Score: 0

      Bob was pretty damn innovative for the, now that I think about it. A user experience unlike any other I've seen before or after. The fact that it was a complete commercial failure really doesn't measure how innovative it was or wasn't. MS tried something very new and different, and it flopped hard.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    15. Re:Papers? by Jherek+Carnelian · · Score: 1

      MSR has a large pool of talent and the money to push this research endeavor farther than any other company or academic institution could, and that is something exciting.

      Except that MS will just patent anything these guys come up with, making the information useless for another ~20 years by which point it will be obsolete anyway.

      I'd prefer that MSR not be doing work on anything useful, that way others who aren't so patent hungry can actually produce something useful to the rest of the world.

    16. Re:Papers? by D3m3rz3l · · Score: 1

      Microsoft Research dominates other areas of computer science as well. For instance, check out how many papers from MSR was accepted at SIGGRAPH 2005. Or check out their NLP and AI research. MSR hires some of the brightest minds in computer science research and provides them with a *lot* of money and a completely free rein to do whatever they want. Furthermore, a lot of the research is then published in open conferences. Don't underestimate MSR. Although a lot of MSR projects don't directly translate into shipping projects, many ideas from MSR do filter down to products as time passes.

    17. Re:Papers? by Wesley+Felter · · Score: 1

      You are screwed. Even universities are getting into the "patent everything" game.

    18. Re:Papers? by Anonymous Coward · · Score: 0
      Please keep in mind that MS Research is quite a different beast than the production departments of MS. MS Research does a lot of respected work. They also employ some of the most reputable researchers in software and OS development


      brilliance in the service of evil is still evil.

    19. Re:Papers? by Anonymous Coward · · Score: 0

      Everything you mentioned about Hoare, Lamport, and Cardelli, I remember knowing about when I was in grad school 20 years ago. (I'm not familiar with the other two.) Butler Lampson and Jim Gray also spring to mind as luminaries associated with Microsoft Research.

      I think it's admirable that Microsoft provides these respected figures with positions and salaries. I don't know if I'd cite them as current reasons not to underestimate Microsoft Research.

    20. Re:Papers? by guisar · · Score: 1

      If only I hadn't just used all my moderation points; I'd mod this up six ways to Sunday. Who knew (not I! and maybe not some of you reading this) one could find researchers in MS employ who are substantive to the point of being fascinating. Leslie Lamport's site, for instance, is well worth a scan. I find it amazing MS is willing to invest in people of this quality.

    21. Re:Papers? by HawkingMattress · · Score: 1

      This Tony hoar guy looks nuts. I mean, look at that... was he wearing his pajamas, or did he stole his wife sticking ? And why did he put this protograph on his bio ? Even the worse geek would take more care of what he gives to see. He must of an ancient, forgotten species. The uber alpha geek, or the Meta Punk Geek Granny ! Anyway, i like his pants.

    22. Re:Papers? by GileadGreene · · Score: 1

      Peyton-Jones and Meijer are extremely active in the functional programming community. Hoare is getting on towards retirement these days, but still actively contributes to the advancement of concurrency theory (and programming theory in general - see his work on "Unifying Theories of Programming"). Lamport is mostly focused on his Temporal Logic of Actions (TLA) as a method for formally specifying concurrent systems these days, and has done a bunch of work with (IIRC) Intel on processor design. I have no idea what Cardelli is up to these days, but I know he's still active. I mentioned the results that you "knew about 20 years ago" mostly because they are considered pretty seminal and there's a good chance most people have heard of at least some of them. We probably won't know if any of their current work is as seminal until it's had a chance to percolate out into the CS community.

    23. Re:Papers? by blackpaw · · Score: 1
      brilliance in the service of evil is still evil

      See this way too often on slashdot. You stupid fuckers have no idea of what evil is, you'd crap your pants if you ever ran into a real nutter.

    24. Re:Papers? by drsmithy · · Score: 1
      brilliance in the service of evil is still evil.

      For fuck's sake.

      Hitler was evil. Pol Pot was evil. Stalin was evil.

      Microsoft is a standard business operation. Hell, they're not even towards the "bad" end of that scale like, say, Nike, Nestle or De Beers are.

      (Although, at least by calling Microsoft "evil" you demonstrate how small the pinhole through which you view the world is, and warn others of your incredibly insulated existence.)

  2. Oh, let me be the first to say it! by RobertB-DC · · Score: 4, Funny

    I've heard that Microsoft Singularity sucks.

    (Go ahead, mod me down... I deserve it.)

    --
    Stressed? Me? Of course not. Stress is what a rubber band feels before it breaks, silly.
    1. Re:Oh, let me be the first to say it! by Anonymous Coward · · Score: 1, Funny

      Mod you down? I'm just bitter you got to that joke first!

    2. Re:Oh, let me be the first to say it! by Anonymous Coward · · Score: 0

      Does this mean that the release date will be severly dialated?

    3. Re:Oh, let me be the first to say it! by Saeger · · Score: 1, Informative
      Microsoft's Singularity is also the antithesis of accelerating intelligence towards the technological Singularity.

      Also - just great - now my Google News Email Alerts for the "singularity" keyword will be poisoned with MS' chaff. Maybe next week they'll come out with a "Nanotech" brand mouse too.

      --
      Power to the Peaceful
    4. Re:Oh, let me be the first to say it! by moviepig.com · · Score: 1
      I've heard that Microsoft Singularity sucks.

      There is, of course, another sort of singularity ... "when technological progress [accelerates] due to the advent of superhuman intelligence..."

      Maybe this new Microsoft thingie is that.

      --
      Seeing bad movies only encourages them. Watch responsibly
    5. Re:Oh, let me be the first to say it! by NickFortune · · Score: 3, Funny

      Is the name not a reference to their policy on IP? They pull in ideas from all over, but none of them ever make it back over the threshold....

      --
      Don't let THEM immanentize the Eschaton!
    6. Re:Oh, let me be the first to say it! by Anonymous Coward · · Score: 0
      I've heard that Microsoft Singularity sucks.


      Didn't somebody once say that a gravitational singularity satisfies all the technical requirements for the location of Hell? Very suitable.

    7. Re:Oh, let me be the first to say it! by leuk_he · · Score: 1

      Well you deserve your + 5 funny, however my first thought was about this sigularity Where an superior AI becomes selfaware and decides that humans are no longer important. this is a concept that is long known and together with the gray goo an hard to imagine future fear for humanity.

    8. Re:Oh, let me be the first to say it! by Anonymous Coward · · Score: 0

      In Mozilla 1.7.8 (on Linux) this link (moviepig.com) takes you to an all-black screen with the title "MoviePig Login".

    9. Re:Oh, let me be the first to say it! by moviepig.com · · Score: 1

      Didn't realize that, thanks. FWIW, the site is Flash-based --pretty much has to be-- but, of course, the Black Hole you describe is not how we'd like to handle an incompatibility...

      --
      Seeing bad movies only encourages them. Watch responsibly
    10. Re:Oh, let me be the first to say it! by The+Wooden+Badger · · Score: 1
      Didn't somebody once say that a gravitational singularity satisfies all the technical requirements for the location of Hell? Very suitable.

      Two observations: First, they should have used Singularity instead of windows all along. Second, if you take market share and apply it to life, Most of the planet is going to/already in hell.

      --
      Heroscape, it's like legos combined with anachronistic wargames.
    11. Re:Oh, let me be the first to say it! by devross · · Score: 1

      You may not be too far off base.

      ...designed with emphasis on dependability instead of performance

      If Microsoft is going to do to dependability what they did to performance...It may very well cause this solar system to collapse in on itsself.

      --


      If these walls could talk they'd probly still ignore me. --MF DOOM
    12. Re:Oh, let me be the first to say it! by quanticle · · Score: 1

      Is the name not a reference to their policy on IP? They pull in ideas from all over, but none of them ever make it back over the threshold....

      To extend your analogy, like a black hole, MS pulls in information from all around it and releases it in mangled form. Look at Monad, their new scriptable shell. Is it not a bastardized version of the scriptable shells that have been available on Unix for years? And now with Singularity, they're trying to copy the Mac OSX microkernel architecture.

      --
      We all know what to do, but we don't know how to get re-elected once we have done it
    13. Re:Oh, let me be the first to say it! by technodolt · · Score: 1

      AFAIK Monad is actually, as far as interfacing with the OS it's applicable to, more useful than several of the currently popular *nix shell scripting languages... for reference see this LONG article.

      --
      "It is the classic fallacy of our time that a moron run through a university and decorated with a Ph.D. will thereby cea
  3. another longhorn? by amacachi · · Score: 1, Troll

    so theyre building from the ground up, just like they were going to with longhorn. whoop de do

    1. Re:another longhorn? by filesiteguy · · Score: 4, Informative
      Nah, that was XP, which was built from the ground up. No relation at all to NT.

      Come to think of it - has MS EVER written their own OS from scratch?

      • DOS - Borrowed from Tim Patterson's QDOS.
      • Windows - Shell extention to DOS
      • Xenix - AT&T/Berkley clone
      • OS/2 - Co-built with IBM
      • NT / XP / Vista - Built off of OS/2

      Go figure.

    2. Re:another longhorn? by Overly+Critical+Guy · · Score: 5, Interesting

      This is just a research OS written in C#.

      Microsoft Research is always making things Microsoft never uses. Remember all the 3D navigator stuff they were crowing about years ago?

      I think Microsoft Research is a place to keep eggheads working and happy so they don't go working somewhere else.

      --
      "Sufferin' succotash."
    3. Re:another longhorn? by just_another_sean · · Score: 1

      NT / XP / Vista - Built off of OS/2
      I beleive you menat to say "Built off of VMS" here.

      --
      Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
    4. Re:another longhorn? by zootm · · Score: 2, Informative

      A few things they've come up with have been used (ClearType off the top of my head, and quite a few usability things, although I'm sure there's more), but it is quite disappointing that there's not been more — the quality and originality of the ideas that come out of Microsoft Research is really quite surprising.

    5. Re:another longhorn? by Anonymous Coward · · Score: 3, Interesting
      Come to think of it, has an written from scratch OS worked?

      CP/M. Some device specific OS's like the C64. The Apple Lisa (which begat the MacOS 1-9). I'm not even sure I'd count Unix, since there's so many flavors all based on something from before. Even Linux was heavily dependant on GNU, which pre-existed it.

      Look at the failures. BeOS. Rhapsody. Plan 9, etc.

    6. Re:another longhorn? by AKAImBatman · · Score: 1, Insightful

      NT / XP / Vista - Built off of OS/2

      Actually, NT was a kitbash of a VMS kernel with OS/2 usermode components, which themselves were "upgrades" to Windows 3.1 components, which were mostly "simple" concepts stolen from Mac OS. Confused yet?

      Now take Windows 95 (which was Windows 3.1 running in full protected mode, but with a new UI and a Virtualized DOS window) and bash it together with NT 3.51. Remove various security considerations and compile the graphics subsystem into the kernel and you have the makings of NT 4.0.

      2000 and XP have since reflected that Microsoft has experienced no major increases in technology. Thus 2000 bashed various bits of Unix into itself (to make it "Enterprise Ready") and XP just added lots'o'pretty-stuff and a Win95 virtualizer.

      Now if Microsoft manages to get their HotOS into production (not bloody likely, considering that Microsoft Research is merely a place for good researchers to die) then Microsoft will have managed to reinvent Symbolics LISP from 20+ years earlier. Yay for progress!

    7. Re:another longhorn? by objekt · · Score: 2, Interesting

      BeOS worked well, still does, actually. And if Apple had bought BeOS it wouldn't be considered a failure.

      --
      -- Boycott Shell
    8. Re:another longhorn? by AKAImBatman · · Score: 1

      s/HotOS/Singularity/g

      I saw the conference above and it got stuck in my head. :-P

    9. Re:another longhorn? by squiggleslash · · Score: 1
      Probably not. There is actual OS/2 code in the NT series of OSes, relating to its original aim of being OS/2 V3. There's not much, because that plan didn't last for very long. But a lot of the original OS/2 1.1 sans-presentation manager code sits, unused, in the userland.

      VMS's "relationship" with NT has to do with Dave Cutler, a respected former DEC engineer who worked on later versions of VMS, being the primary designer of the original NT kernel, and using many of the same ideas (as you'd expect him to do.) Some people, as you appear to suggest, have chosen to go further than this and claim there's code from VMS in NT. This is fairly ludicrous and the evidence behind it appears to be based upon innuendo (my God! They shared a designer!) and taking certain facts (such as some design decisions being similar) to mean far more than "Cutler designed both" and "Most OSes have equivalents anyway, dumbass" (dumbass label applied to "Mark Russinovich" - wow, both OSes have a kernel except VMS's is called "sys.exe" and NT's is called "ntoskrnl.exe", with proof like that, who needs intelligence? I mean, they've got to be clones! They both have kernels, and ASTs, and paged memory, and...)

      I've seen this conspiracy theory repeated ad-nausium on Slashdot. It's stupid. It needs to die, quietly, as an anti-Microsoft myth that's entirely unnecessary given the real bad things they've done. All it actually does is hurt the reputation of Dave Cutler, and I don't think that's fair.

      --
      You are not alone. This is not normal. None of this is normal.
    10. Re:another longhorn? by Jerry+Coffin · · Score: 5, Insightful
      Come to think of it - has MS EVER written their own OS from scratch?

      Better question: when's the last time anybody wrote an OS from scratch?

      As far as I can see, the answer to that is really "never". Before there were OSes, there were collections of macros to act like device drivers and such. The first OSes were based on those, and added slightly more uniform interfaces and such.

      Pretty much everything since can be traced back to something previous.

      DOS - Borrowed from Tim Patterson's QDOS.

      Windows - Shell extention to DOS

      Xenix - AT&T/Berkley clone

      OS/2 - Co-built with IBM

      NT / XP / Vista - Built off of OS/2

      DOS 1.0 was based on QDOS, but DOS 2.0 was essentially a complete rewrite that was really based much more closely on UNIX than on QDOS.

      In fairness it should also be added that QDOS was based on (according to some, just a re-compile of) CP/M. Lest any CP/Mers get all holier-than-thou about it, in his original announcement letter about it to "Doctor Dobb's Journal of Computer Calisthenics and Orthodontia", Gary Kildall openly stated that CP/M was derived from DEC RT/11. I'll assume there aren't enough DECies left to bother debunking the notion that RT/11 was entirely original.

      I'd say the others are much the same way: on one hand, MS contributed more originality than you imply, and on the other hand, others contributed less than you imply.

      --
      The universe is a figment of its own imagination.

      --
      The universe is a figment of its own imagination.
    11. Re:another longhorn? by B'Trey · · Score: 1

      If a frog had wings, he wouldn't bump his ass on the ground every time he jumped. The bottom line is that, however technologically innovative and well crafted it was, BeOS was a failure. It's been tossed on the junk heap of history and, while there are a few diehard fans who may keep it breathing on life support for awhile longer yet, the chance of it ever being succesful in any meaningful way is so remote as to be dismissed out of hand. You can argue that this is injust - that it was a fine OS which deserved a better fate, and I certainly won't argue with you. But regardless of what shouldda/wouldda/couldda happened, what DID happen is that BeOS was a flash in the pan with lots of hype that quickly faded into oblivion.

      GP post was correct so far as I can tell. Every succesful (where succesful means it actually made it into significant use in the real world) OS was a refinement of a previous attempt, and every new, innovative, designed from scratch OS project has ended in dismal failure, usually bankrupting the designers (or at least the corporation they formed) in the process.

      --

      "The legitimate powers of government extend only to such acts as are injurious to others." Thomas Jefferson.

    12. Re:another longhorn? by jcr · · Score: 2, Informative

      Better question: when's the last time anybody wrote an OS from scratch?

      Let's see.. There's EROS and Coyotos, just to name two within the last decade.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    13. Re:another longhorn? by kisrael · · Score: 1

      Yeah, it would be cool if monopoly-ish Microsoft could kind of justify its existence with a Bell Labs type semi-pure research facility...

      --
      SO YOU'RE GOING TO DIE: The Comic for Dealing with Death
    14. Re:another longhorn? by LLuthor · · Score: 3, Insightful

      I am going to be modded troll for this I am sure, but I have to say it anyway.

      How many OSes have ever been written from scratch?

      I can think of only 3, none of which has even 0.1% market share. In fact, Plan9 is the only one of them alive.

      What is the big deal with bashing microsoft for copying ideas from people?

      Isn't that what OSS is built around, copying good ideas?

      --
      LL
    15. Re:another longhorn? by heson · · Score: 1
      Any OS needs apps to hit. No previous built-from-scratch had any chance of gaining critical mass of apps, the backwards compability was needed. But now, the open source flora is finally large enough for a built from scratch OS to take off. The porting work would be huge [1] but it would be possible.

      [1] Depending on the definition of "built from scratch" implementing API's to make it enough unix-like would speed up the porting.

      I hope you get my point, even if Im explaining it a bit messy.

    16. Re:another longhorn? by shmlco · · Score: 5, Insightful
      You mean the way the FOSS community has managed to reinvent Unix from 30 to 40 years earlier? Yay for progress!

      Seriously, ALL operating systems borrow concepts from earlier versions and the existing state of the art. Trying to determine the degree (or not) of "innovation" is akin to arguing about the number of angels that can dance on the head of a pin, with no prior agreement as to the size of an angel...

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    17. Re:another longhorn? by cpt+kangarooski · · Score: 1

      Actually the Mac was in development before the Lisa project adopted similar UI concepts and goals. They were both worked on at the same time, with a lot of ideas going from one to the other. The Lisa happened to be released first, but it's incorrect to think of it as being the source of the Macintosh.

      (Also, pre System 6 version numbers are wierd. Generally, people wouldn't talk about the version of the OS, so much as the versions of the Finder and System. E.g. version 5 of the OS was comprised of System 4.2 and Finder 6.0. System 6 was much more coherent, and System 7 even more so.)

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    18. Re:another longhorn? by linguae · · Score: 2, Informative

      Err, Rhapsody was based off of OPENSTEP, which is based off NEXTSTEP, which is based off 4.2BSD (based off AT&T Unix 32V) and Mach from CMU. Mac OS X is based off of Rhapsody. Rhapsody was never released to the public, and the only reason why Rhapsody "failed" (i.e., Apple decided to abandon it and do a different approach with transforming OPENSTEP to OS X) is because Rhapsody would have forced developers to develop all of their applications for OPENSTEP APIs (now known as Cocoa). Developers didn't feel like re-writing all of their old Mac OS applications, so Apple had to spend the next few years developing Carbon (which contains much of the old Classic APIs, just updated for OS X).

      Plan 9 is a new operating system, but much of it is based off the concepts of Unix. Plan 9 improves from Unix in many ways. It "failed" in the sense of doesn't have any market share, but Plan 9 wasn't about taking over the world. It is just a research project, and many of the concepts invented there (such as UTF-8 support and /proc) has been used in many other OSes and applications. Plan 9 has a very neat design and environment.

      In a sense, all of the modern OSes that we use now are based off of a predecessor OS, either by sharing code or sharing concepts/functionality.

    19. Re:another longhorn? by Al+Dimond · · Score: 4, Informative

      Windows NT and VMS isn't a conspiracy theory or a myth. It's not dirty.

      Recently I heard a talk about the Windows kernel given by a guy from Microsoft. At the beginning of a talk, he said, "There are only two operating systems that matter." After the audience buzzed for a while, saying to eachother, "That jerk, Linux matters too!" or "That jerk, OS X matters too!" or "That jerk, BSD matters too!" He said something like, "You guys don't seem to like that, so what's the third?" One guy shouted out, "Windows!" The MS guy said, "Well, if you mean 'evil Windows', that is, Win95/98/ME, then it probably isn't even third. There are two operating systems that matter and they are Unix and VMS." He explained that for the most part ideas from VMS, rather than from Unix, shaped the design of the NT kernel. Looking at the Russinovich article, many of the things he lists as similarities are also similarities with Unix and many are similarities with any modern OS. Some, like the Object Manager, are specific to VMS and Windows. But overall, as long as DEC and MS came to some kind of agreement over any shared concepts or code, it's no knock on Microsoft, just as it's no knock on Linus for implementing a Unix-like OS. Better to borrow some things from a proven design and get a good product than to forge off on your own and make wierd mistakes.

    20. Re:another longhorn? by loose_cannon_gamer · · Score: 1

      I guess this leaves me wondering when they'll finally figure that they need to be building their operating systems from the sky down. That would solve everything.

      --
      In Soviet Russia, us are belong to all your base.
    21. Re:another longhorn? by Anonymous Coward · · Score: 0

      Palm OS, QNX, the japanese thing.

    22. Re:another longhorn? by AKAImBatman · · Score: 2, Interesting

      VMS's "relationship" with NT has to do with Dave Cutler,

      You're ignoring the fact that the relationship was Dave Cutler, and 20 of his team members.

      a respected former DEC engineer who worked on later versions of VMS, being the primary designer of the original NT kernel, and using many of the same ideas (as you'd expect him to do.)

      The story actually goes much farther than that. You see, when Cutler was working at DEC, he was pushing a complete rewrite of the VMS Operating System. His new version of the OS would have all kinds of neato features that no one had ever seen before. DEC gave him the go-ahead and development commenced. After the project had gotten far along, DEC decided to pull the plug on it, and moved Cutler elsewhere. Cutler (predictably) quit.

      Microsoft then sapped up Cutler on the agreement that Microsoft would also hire all the team members who'd been working on the Next-Gen VMS project with him. Microsoft agreed, and development on "Windows NT" (which doesn't actually mean anything, the marketdriods just liked the "NT" letters) began in earnest.

      DEC eventually found out about the whole thing, and wanted to sue. However, an agreement was reached to where Windows NT would run on Digital Alpha hardware. DEC *thought* they got a good deal (all the technology, none of the development costs) but didn't realize quite the deal they were getting into. The Alpha version of NT worked, but absolutely no one targetted software to it. Oops.

      Some people, as you appear to suggest, have chosen to go further than this and claim there's code from VMS in NT.

      It's irrelevant if that is true or not. (Though it might be, given the amount of resources directly transferred to Microsoft.) What's relevant is the fact that each engineer carried a metric boatload of proprietary technology to another company. That's simply not legal for employees, especially when they're under contract. Thus Microsoft benefitted from all the work that DEC had already paid for.

      As for the similar naming scheme, I had to chuckle at that. I had never read the Windows NT Magazine article on this until just now. While his ducks are mostly in order, the comparisons are a bit silly. No, I actually learned from a much more interesting source: DiskKeeper. They used to make Defrag software for VAX VMS, then converted it to run on NT when it came out. Funny thing that. You'd almost think that the two systems were so similar that it would be a natural port, now wouldn't you?

      (Sarcasm aside, DiskKeeper actually had to distribute a custom version of NT 3.x because Microsoft hadn't provided any method of relocating file system blocks. Microsoft eventually worked this feature into NT 4.0.)

    23. Re:another longhorn? by zootm · · Score: 1

      The cynicism is strong in you, my son. :)

    24. Re:another longhorn? by AKAImBatman · · Score: 1

      Of course. I'm just amused that Microsoft has made "a sudden discovery!" that real OS designers have known about for an incredibly long time. In fact, OSes designed in C are actually a step back from some of the Mainframe OSes designed in languages such as ALGOL. The key was that C could give you maximum performance by letting you perform hacks no sane person would ever make. But it was fast, so people ran with it.

    25. Re:another longhorn? by Anonymous Coward · · Score: 0

      Um... Unix, back in the early 70s, for one?

    26. Re:another longhorn? by shmlco · · Score: 1

      Cool. I'm going to CompUSA this afternoon. I'll have to pick up a couple of copies and see what they're like........

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    27. Re:another longhorn? by NullProg · · Score: 1

      A few things they've come up with have been used (ClearType off the top of my head,

      ClearType was re-invented by Microsoft. It was done first by Apple. Now what innovation has Microsoft shown?

      http://grc.com/ctwho.htm Sub-Pixel Font Rendering

      Enjoy,

      --
      It's just the normal noises in here.
    28. Re:another longhorn? by ChrisGilliard · · Score: 1

      Better question: when's the last time anybody wrote an OS from scratch?

      Minix and Linux

      --
      No Sigs!
    29. Re:another longhorn? by Darth · · Score: 1

      Look at the failures. BeOS. Rhapsody. Plan 9, etc.

      Rhapsody wasnt really a from scratch OS, so it shouldnt be included in this list.

      Plan 9 wasn't a failure. The goal with Plan 9 was never to be a commercially successful operating system. It's a research operating system. The fact that a few companies have used it for commercial products does not mean it must succeed commercially to have fulfilled its designers' objectives.

      BeOS did fail, but it never really had a chance to succeed. It was killed by predatory practices before it had a chance to succeed or fail on it's own merits. As a result, the only conclusion i would draw from BeOS is that a totally new operating system cannot succeed in a market where a monopoly that employs predatory tactics holds sway.

      --
      Darth --
      Nil Mortifi, Sine Lucre
    30. Re:another longhorn? by Anonymous Coward · · Score: 0

      If you read Slashdot enough, you'll know that Linus simply wrote the Linux kernel. An OS is more than a kernel.

    31. Re:another longhorn? by orasio · · Score: 1

      Even Linux was heavily dependant on GNU, which pre-existed it.

      Linux as a kernel is not dependant on GNU.
      "Linux distros" are actually GNU distributions + a Linux kernel, so of course they use GNU, but GNU/Linux is a combination of GNU and another thing, not a post-mortem derivative of GNU.

    32. Re:another longhorn? by zootm · · Score: 1

      So I've seen. "Re-inventing" doesn't change the fact that it wasn't in widespread use in modern systems until then though. And there's other things too, it's just ClearType is an easy one to remember. :)

    33. Re:another longhorn? by Infinityis · · Score: 1

      What about PalmOS and it's kin? Given the scarcity of resources on smaller platforms, it'd imagine it's pretty common to come up with new OSes...

    34. Re:another longhorn? by Fujisawa+Sensei · · Score: 1

      AROS

      :-p
      --
      If someone is passing you on the right, you are an asshole for driving in the wrong lane.
    35. Re:another longhorn? by renfrow · · Score: 2, Insightful

      GP post was correct so far as I can tell. Every succesful (where succesful means it actually made it into significant use in the real world) OS was a refinement of a previous attempt, and every new, innovative, designed from scratch OS project has ended in dismal failure, usually bankrupting the designers (or at least the corporation they formed) in the process.

      Sooooo.... Where is the bad in this if Microsoft does it?

      Tom.

    36. Re:another longhorn? by Jerry+Coffin · · Score: 1
      Better question: when's the last time anybody wrote an OS from scratch?

      Minix and Linux

      I'd have thought it was quite obvious that both were based pretty closely on UNIX -- which, of course, derives a lot from MULTICS. In fairness, MULTICS did have considerably more originality than most -- but an awful lot of its most original ideas have disppeared in the derivatives.

      As far as how close a basis these formed: just to go back to one of the examples up the thread, certainly closer than relationship between Windows NT and OS/2 (not that that means much, since Windows NT is really much more a derivative of VMS than of OS/2).

      --
      The universe is a figment of its own imagination.

      --
      The universe is a figment of its own imagination.
    37. Re:another longhorn? by AKAImBatman · · Score: 1

      And if Apple had bought BeOS it wouldn't be considered a failure.

      Pff. You say that as if it's a bad thing. Apple did much better than they ever possibly could have done by buying BeOS. They got a far more mature, Unix-based OS, AND they snagged key BeOS developers to add cool things like Spotlight. The only real advantage that BeOS had was that it was much faster with Multimedia, something that doesn't matter in a day when it's all hardware accelerated anyway.

    38. Re:another longhorn? by Jerry+Coffin · · Score: 1
      Um... Unix, back in the early 70s, for one?

      As previously noted, largely derived from MULTICS. Admittedly, some of the derivation is by reversal -- i.e. attempting to do exactly the opposite of what MULTICS did. That was obviously true of the name, but only slightly less obviously of many other parts as well. The result is still surprisingly MULTICS-like in many respects.

      --
      The universe is a figment of its own imagination.

      --
      The universe is a figment of its own imagination.
    39. Re:another longhorn? by jd · · Score: 1
      UNIX was a vastly simplified, cut-down version of MULTICS - even the name is a derivative. If I remember my comp sci history, MULTICS was based - to a degree - on TOPS and Project MAC. I can't tell you if either of those was novel or not.


      There are a number of interesting research OS' out there, but I couldn't tell you if any of them were derivative or not. uMicro's Object Oriented OS in the late 80s was pretty interesting. Slow, limted but interesting.


      The Transputer/Occam coupling was intriguing in that it provided a layer that wasn't strictly an OS, but provided the system calls an OS would have. As such, it could be considered totally non-derivative, as there was nothing there to be derived. I miss the Transputer - it was by far the best design of processor for its day, and its fate was a miserable, undeserved one.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    40. Re:another longhorn? by Anonymous Coward · · Score: 0

      "Insightful"???

      PLEASE! AKAImBatman is full of it!

    41. Re:another longhorn? by squiggleslash · · Score: 1

      You're ignoring the fact that the relationship was Dave Cutler, and 20 of his team members.

      I'm not really sure that that's all that relevent, it certainly isn't something I'm either ignoring nor considering important. Whether it's one programmer or a hundred, they either cloned VMS, possibly including source code, or they didn't. I maintain it's improbable that they did.

      Microsoft then sapped up Cutler on the agreement that Microsoft would also hire all the team members who'd been working on the Next-Gen VMS project with him. Microsoft agreed, and development on "Windows NT" (which doesn't actually mean anything, the marketdriods just liked the "NT" letters) began in earnest.

      Which makes the entire story even less of the "NT is just a clone of VMS!" (which is ludicrous, as anyone who's actually used both can tell you. NT and VMS have almost nothing in common except at levels where, frankly, NT and Unix have things in common.) Now, you're trying to claim I'm wrong in what I wrote by raising an entirely different argument, that:

      It's irrelevant if that is true or not. (Though it might be, given the amount of resources directly transferred to Microsoft.) What's relevant is the fact that each engineer carried a metric boatload of proprietary technology to another company. That's simply not legal for employees, especially when they're under contract. Thus Microsoft benefitted from all the work that DEC had already paid for.

      which may or may not be true, but it's irrelevent. The fact is people claim that NT contains VMS code, that it's based on VMS. It isn't. It's not true, it's ludicrous people keep alleging it is. Whether NT may contain similar concepts to an unreleased unfinished operating system intended to replace VMS is simply not relevent to that, and certainly no basis for arguing that NT is based on VMS.

      No, I actually learned from a much more interesting source: DiskKeeper. They used to make Defrag software for VAX VMS, then converted it to run on NT when it came out. Funny thing that. You'd almost think that the two systems were so similar that it would be a natural port, now wouldn't you?

      No, I wouldn't. Let's have a look at the APIs and file systems they'd have had to work with.

      Under VMS, they'd have had to work with the VMS native API, and the VAX file systems.

      Under NT, they'd have had to work with the Win32 API, and the HPFS (for early NTs) and NTFS file systems.

      "Aha!" I pretend to hear you cry, "But NTFS must have been based on the VMS file system, right?" Well, probably not, the available evidence suggests NTFS's designers started with HPFS, something co-developed by IBM and Microsoft for OS/2 well before Cutler got a hand in. More to the point, try comparing them at some point. VMS's FS, while using crude uppercase 40.40 filenames, had some remarkable features, including complete indexed database features (you could specify the record structure of files, define indexes, even something as simple as end-of-line markers could be defined, or removed completely in favour of record-length words, all at an OS/file system level.) There's nothing like that in NTFS, which is much more of a desktop-oriented system, with a slightly modernised file naming convention.

      Likewise, Win32 is based upon the Windows 3.x APIs, which in turn are enhancements of the Windows 2.x APIs (Windows 2.x's APIs largely supplanted the 1.x APIs, which remained largely for backward compatability, so I'm not going to continue the trail, but right now you presumably see where I'm going with this.)

      In other words, neither Cutler, nor the programmers he brought over from DEC had much of a hand in either the API the DiskKeeper people were using under NT, nor the basis of the filesystem the DiskKeeper application was supposedly optimizing.

      Fundamentally, I assume there was nothing easy about the port, certain principles would have remained the same (eg k

      --
      You are not alone. This is not normal. None of this is normal.
    42. Re:another longhorn? by Coryoth · · Score: 5, Informative

      This is just a research OS written in C#.

      No, it's written in Sing# which is an extension of Spec# which is an extension of C#. People really ought to pay more attention to Spec# - it's a nice extension of C# that allows for more formality if and when you require it. It's in the same class of language as SPARK which is an extension of Ada, JML which extends Java with specification semantics, BitC, Extended ML, HasCASL, and I guess to a lesser extent things like Eiffel and D.

      Think of it this way: static types and type signatures for functions allow you to specify things about the software that the compiler can statically check and make sure there aren't any silly errors. The languages listed above (to varying degrees) allow for more exacting specification about the software, and hence you can (with the right tools) do far more comprehensive static checking and ensure various properties of the software. The difference is that, with most of these languages, the amount of specification is optional - you can be as exacting as you want where you need it, and not bother where you don't. It's like a dynamically typed language that lets you declare and use static types (and check them)just for those areas of code where it matters (except you start with static types and can provide more exacting specification where it matters). It's well worth checking out.

      Jedidiah.

    43. Re:another longhorn? by Anonymous Coward · · Score: 0

      > but DOS 2.0 was essentially a complete rewrite that was really based much more closely on UNIX than on QDOS.

      Only like masterbation is to sex. Sorry, takes a bit more than a hierarchical filesystem and moving command arguements into something sensical to be "based much more closely on UNIX".

    44. Re:another longhorn? by Anonymous Coward · · Score: 0

      And we should definitely believe you because you're offering so much counter-evidence.

    45. Re:another longhorn? by Anonymous Coward · · Score: 0

      Subtract one letter from Windows NT (WNT) and you get VMS...coincidence? I think not.

    46. Re:another longhorn? by Anonymous Coward · · Score: 0

      From your own links -
      "EROS combines an unusual collection of facilities into a single package, hopefully in a novel way. Each of these faclities is, in our view, essential to providing scalable reliability, and all of them have appeared in prior systems."

      "Coyotos is a secure, microkernel-based operating system that builds on the ideas and experiences of the EROS project. Much of the code developed for EROS will migrate directly to Coyotos."

      At least they are more honest (or knowledgeable) than you.

      Progress usually stands on the shoulders of giants.

    47. Re:another longhorn? by AKAImBatman · · Score: 1

      Add one letter to HAL, and you've got IBM. Coincidence?

      Oh yeah.

      It's just funny how things work sometimes. :-)

    48. Re:another longhorn? by Blakey+Rat · · Score: 1

      Also BeOS was developed in the early 90s, but they might have started in the late 80s. I'm pretty sure I recall seeing interviews in which the creators said that it was written from scratch.

    49. Re:another longhorn? by Jerry+Coffin · · Score: 1
      Of course. I'm just amused that Microsoft has made "a sudden discovery!" that real OS designers have known about for an incredibly long time. In fact, OSes designed in C are actually a step back from some of the Mainframe OSes designed in languages such as ALGOL. The key was that C could give you maximum performance by letting you perform hacks no sane person would ever make. But it was fast, so people ran with it.

      While I sympathize with your position, I don't think all your statements are particularly accurate. First of all, when UNIX was new, quite a few OSes were still written in assembly language, and computer time was still expensive enough that nearly everybody was quite concerned with efficiency. Even the systems written in higher level languages didn't necessarily use particularly clean languages -- BLISS, JOVIAL and PL/I virtually spring to mind as counterexamples.

      Second, UNIX was originaly oriented far more toward being small and simple rather than attempting to be particularly fast. If (for example) you get a copy of Lion's book and read through the source to UNIX V6, you'll find lots of simplicity at the expense of efficiency. Admittedly, since then a lot of work has been put into improving performance, so the code in current systems has a lot more emphasis on efficiency, but that happened LONG after mainframe OSes written in things like ALGOL were mostly gone and forgotten.

      At the same time, as I said, I am largely sympathetic with your basic position. It's really true that OSes written for big mainframes placed a much higher emphasis on reliability than currently seems to be the case almost anywhere. I can still remember sitting at a terminal and doing a quick check to find that the college's mainframe currently had between 300 and 350 people logged on, and it just kept on chugging -- and this on a machine with (IIRC) about an 8 or 10 MHz CPU and (in round numbers) one megabyte of RAM...

      --
      The universe is a figment of its own imagination.

      --
      The universe is a figment of its own imagination.
    50. Re:another longhorn? by ChrisGilliard · · Score: 1

      I'd have thought it was quite obvious that both were based pretty closely on UNIX

      Well, yes, it's obvious that both use fundamental concepts that were derived from UNIX, but they were not written off an existing codebase of UNIX. If your question is: "When's the last time anybody wrote an OS from scratch without using operating system concepts derived from other systems?", I'd say that has never and will never happen. Even Windows uses concepts originated in UNIX. For instance, Windows has a file system, that concept had already been implemented in UNIX, windows has a memory management unit, that was in UNIX, windows the concept of process scheduling, that was in UNIX. This does not mean that Windows was based off of UNIX. I'm sure if you analyze this new Singularity OS, there are features from Windows, UNIX, etc.

      --
      No Sigs!
    51. Re:another longhorn? by tzot · · Score: 1

      Based on the "old" saying (one such incarnation can be found in: http://www.urbandictionary.com/define.php?term=Win dows )

      Windows: A 64-bit revamping of a 32-bit extension for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor written by a 2-bit company that can't stand 1 bit of competition.

      --
      I speak England very best
    52. Re:another longhorn? by admactanium · · Score: 1
      BeOS worked well, still does, actually. And if Apple had bought BeOS it wouldn't be considered a failure.
      actually, it would probably be considered a failure along with the now-dead company known as apple. if apple had bought beos rather than next, jean-louis gasse would have been at apple rather than steve jobs. jobs' insistence on things being "just right" saved the company. the jellybean imac was the savior of the whole company. i have a friend who worked closely with apple at the time of the transition and they were pretty close to being on a month-to-month basis of surviving. so if we were to revise the history, beos would probably be even more dead than it is now along with apple computer and the ipod wouldn't have existed.
    53. Re:another longhorn? by Anonymous Coward · · Score: 0

      And it's still not funny.

    54. Re:another longhorn? by Anonymous Coward · · Score: 0

      Sure. That said, it was still written from the ground up by two guys in their spare time.

    55. Re:another longhorn? by amliebsch · · Score: 1

      That doesn't give enough credit, I think. Good sub-pixel rendering of arbitrary vector alogrithms on an RGB display (and one that works well with color combinations other than white-on-black) is a significantly greater challenge than the bitmapped sub-pixel fonts that the Apples used. Though the concepts are similar in theory, the innovations in going from one to the other are, IMO, quite substantial and deserve more than your derision.

      --
      If you don't know where you are going, you will wind up somewhere else.
    56. Re:another longhorn? by Anonymous Coward · · Score: 0

      If you don't count influences then BeOS--inspired by Xinu--was written from scratch as was Linux.

      And don't bring up the whole 'Linux is a kernel/BeOS is an OS' because BeOS used GNU tools too.

    57. Re:another longhorn? by Anonymous Coward · · Score: 0
      I'll assume there aren't enough DECies left to bother debunking the notion that RT/11 was entirely original.
      Hold on there, Sonny Jim, I worked on RT/11 back in the day, and I tell you it WAS entirely ... I've got the proof right here in my lab notes ... wait .... Drat. Now, where are those dang spectacles? Left 'em right there on the desk.... Sit tight there, whippersnapper, I'll deal with you in a moment.
    58. Re:another longhorn? by jcr · · Score: 1

      From your own links -
      "EROS combines an unusual collection of facilities into a single package, hopefully in a novel way. Each of these faclities is, in our view, essential to providing scalable reliability, and all of them have appeared in prior systems."


      The question at hand was whether any OS's had been written from scratch. EROS didn't re-use code from from previous operating systems. That qualifies as "written from scratch" as far as I'm concerned.

      At least they are more honest (or knowledgeable) than you.

      Fuck you too, sunshine.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    59. Re:another longhorn? by Overly+Critical+Guy · · Score: 1

      No, it's written in Sing# which is an extension of Spec# which is an extension of C#.

      Cough. So it's written in C#. :)

      Even the Channel 9 presentation linked to on the page is entitled, "Singularity: A research OS written in C#."

      --
      "Sufferin' succotash."
    60. Re:another longhorn? by jcr · · Score: 1

      And if Apple had bought BeOS it wouldn't be considered a failure.

      Apple, or Be?

      If Apple had gone with BeOS, Apple wouldn't exist today.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    61. Re:another longhorn? by Anonymous Coward · · Score: 0

      Symbian OS?

    62. Re:another longhorn? by jd · · Score: 1
      Oh, I'll agree with that, certainly. And if you use the definition of "innovative" that I've suggested elsewhere (ie: that it has a non-obvious, non-derivative creative element that extends without being an extrapolation and is integral without being an interpolation), then Unix would be innovative.


      It's still a derivative, in the sense that it is not wholly original, but it is not wholly derivative, it has innovative aspects that were ingenius and original. To me, it is one of the clearest cases of where you can have it both ways.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    63. Re:another longhorn? by Maxhrk · · Score: 0

      then Job will attempts to do OpenApple next to Linux. :)

    64. Re:another longhorn? by ScottKin · · Score: 1, Informative

      Some amplification:

      It is true that if you compare the base-level architecture of VAX VMS to NT 3.1, you *will* see striking similarities, including the mutation of the RPC to an "LPC" using the precursor to Named Pipes in NT 3.1; however, as a former member of the NT 3.1 DevTeam under Ken Gregg and S. Somassegar I can make certain categorical statements:

      1) There is no VMS code within NT, as far back as NT 3.1

      2) The *only* bits of OS/2 that were included in NT 3.1 were for the OS/2 Subsystem to provide for the running of OS/2 Character-mode applications, just as there are POSIX bits to provide for NT 3.1's support for POSIX & POSIX-compliant applications.

      3) NT was *not* developed from OS/2, but were developed in-parallel - which caused the rift between IBM and Microsoft and the dropping of Microsoft's involvement in OS/2.

      4) "NT" stood for "New Technology", which is exactly what NT was within the PC Industry. The ideas may have migrated when Dave and his team moved to Microsoft from DEC, but NT was totally new from the ground up.

      Regarding Mr. Russinovich's "analysis"; he's about as far off the target as the linux-fanboys make their yearly claim that "Linux will be fully accepted by regular computers users this year".

      If you *really* want the whole story about NT and it's development, read "SHOWSTOPPER" - available at Amazon via this URL:

      http://www.amazon.com/exec/obidos/tg/detail/-/0029 356717/qid=1131056728/sr=8-1/ref=pd_bbs_1/103-8665 403-3011016?v=glance&s=books&n=507846

      Enjoy!

      --ScottKin

      --
      I don't give a rat's behind about "karma" here or anywhere else. Don't like what I have to say here? Deal with it!
    65. Re:another longhorn? by Richard+Steiner · · Score: 1

      The 16-bit OS/2 was a joint MS/IBM project, but the 32-bit OS/2 was not, and that's the one which is typically still in use. The MS code is long gone.

      --
      Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
      The Theorem Theorem: If If, Then Then.
    66. Re:another longhorn? by pcnetworx1 · · Score: 1

      I can still remember sitting at a terminal and doing a quick check to find that the college's mainframe currently had between 300 and 350 people logged on, and it just kept on chugging -- and this on a machine with (IIRC) about an 8 or 10 MHz CPU and (in round numbers) one megabyte of RAM... All I can say for a comparison to put this statistic to an even more impressive degree, an original Nintendo GAME system had a 4 mhz processor.... (aka NES) So could you imagine 350 people sharing time between 3 Nintendos? Probably not.

    67. Re:another longhorn? by whatteaux · · Score: 1

      Come to think of it, has an written from scratch OS worked?

      I thought OS/360 was written from scratch (yes?) and it worked. And its descendants (the MVS family of OSs, including OS/390 and z/OS) also work. Code that ran on OS/360 40 years ago will still run just fine on z/OS today.

      When I shake my walking frame at young people today and tell them this, they just don't believe me. Toy-computer weenies, the lot of them. Bah!

    68. Re:another longhorn? by patonw · · Score: 1

      I think the question really should be "when has a commercial OS been written from scratch by its manufacturer?"

      Making radically new OSes does happen... in CS research but those aren't very practical for your average Joe to plop on his Dell and start using. A commercial company takes an existing OS (where someone else has applied obscure algorithms and data structures) and add "value" to it.

      I'm surprised you didn't mention Apple and OS X. They took a solid server system and turned it into a really slick consumer desktop, but the innovation wasn't "inventing" an entirely new kernel or implementing a new memory management scheme.

    69. Re:another longhorn? by Anonymous Coward · · Score: 0
      This is just a research OS written in C#.

      or you're really meaning Java JDK1.1?

    70. Re:another longhorn? by Art+Tatum · · Score: 1

      I don't disagree with your main point, but the reason people are so annoyed by Microsoft's use of others' ideas is that Microsoft then proceeds to claim that the afore-mentioned ideas sprang fully formed from the gigantic brain of Bill Gates, referred to reverentially as "God Almighty." It's their arrogance and lack of respect for those who came before that really annoys me.

    71. Re:another longhorn? by Anonymous Coward · · Score: 0

      It's pretty easy to make a blanket statement like that, but what are you basing it on?

      Microsoft Research funded the XEN project but people tend to forget that as they compare XEN to Virtual Server and bash MS etc etc etc.

      Microsoft Research is where the CRL and .NET sprung from years ago.

    72. Re:another longhorn? by ishepherd · · Score: 1
      ...which was originally EPOC OS 5, built by Psion, the culmination of their PDA software work going right back to 1984.

      Now there was an innovative company - typically for a UK computer company, they were far better at developing tech than at selling it. The exact converse is what seems to bring success in the world, sadly...

      --
      fud, notfud, yes, no, maybe
    73. Re:another longhorn? by child_of_mercy · · Score: 1

      Month to month?

      They were always sitting on a huge cash pile. (minority shareholders might have had views on the best way to spend tt though)

      --
      'There is a Light that never goes out.'
    74. Re:another longhorn? by McGiraf · · Score: 1

      Microsoft: borrow, modify so it is incompatible with the standard , hide the source, pretend they invented it, then proceed to sell it to you every few years or so.

      OSS: well you see the point ...

    75. Re:another longhorn? by harlows_monkeys · · Score: 1
      NT / XP / Vista - Built off of OS/2

      Well, if you consider reusing the code name that they were going to use for the next generation of OS/2 and having a subsystem that could run old OS/2 console programs (similar in technology to the DOS subsystem) to be "built off of", then yes.

      However, if "built off of" requires actually having some technical connection (code, design, or what not), then NT is not built off of OS/2.

    76. Re:another longhorn? by circusfire · · Score: 1

      That sounds more like a whorehouse

    77. Re:another longhorn? by DavidBurns · · Score: 2, Insightful

      Parent wrote:

      --
      OS/2 - Co-built with IBM

      NT / XP / Vista - Built off of OS/2
      --

      Correction; NT was not "Built off of OS/2" but was designed by David Cutler based on concepts in VMS. About the only commonality between OS/2 and NT is their shared heritage of compatibility with MS-DOS.

    78. Re:another longhorn? by Coryoth · · Score: 1

      If you desperately want to think of it that way, fine. C++ is an extension of C. It is C extended to allow object oriented semantics and syntax. Spec# is an extension of C# . It is C# esntended to allow formal specification semantics and syntax.

      I guess there are people who refer to things written in C++ as being "written in C", but generally it gives a somewhat false impression. It'll do as an explanation for people who aren't aware what the extended functionality supplies and what the resulting implications are for te software. It is, at best, just a quick explanation you provide for people who don't really know what they're talking about though.

      Jedidiah.

    79. Re:another longhorn? by objekt · · Score: 1

      The iMac was in development for years before Jobs returned. Computers have a long development cycle, believe it or not.

      --
      -- Boycott Shell
    80. Re:another longhorn? by kan0r · · Score: 1

      Wait a second! WinNT, the first partly-usable OS from Redmond was designed by the VMS developers. They were bought by MS, so you *could* say, *technically* it was designed by MS, but those developers were in fact all long-year VMS developers.

  4. Broken by Toccy · · Score: 1

    The first link is broken. To microsoft's site.

    1. Re:Broken by boy_afraid · · Score: 0

      Is there any more IRONY for a need of Singularity than a link broken on thier web site?? HAHAHA!

    2. Re:Broken by cbc1920 · · Score: 1

      It seems to break in Firefox but works on Safari. The website is just non-compliant, not slashdotted.

  5. Singularity... by pwnage · · Score: 2, Funny

    "Because when we blue screen, all of your data goes down into a black hole."

    --
    Reminder: Apple owns 1/255th of the internet.
    1. Re:Singularity... by NanoGator · · Score: 5, Funny

      "Because when we blue screen, all of your data goes down into a black hole."

      Tee hee giggle snort. That was funny! I'd say more, but Full House is on! Cya!

      --
      "Derp de derp."
    2. Re:Singularity... by Anonymous Coward · · Score: 0
      I can't stand it, I just gotta know : are you a Candace or a Kimmy?

      Knowing /., you're probably into "uncle" Jessie.

    3. Re:Singularity... by Enrique1218 · · Score: 1

      damn!! You beat me to the singularity joke.

      --
      You don't have to be smart to use a Mac, you just have to be smart enough to buy one
    4. Re:Singularity... by utexaspunk · · Score: 1

      Dude... Candace was the actress's name. DJ was the character. Geeeez- Can't people get basic Full House trivia right anymore?

    5. Re:Singularity... by Anonymous Coward · · Score: 0

      Thanks for your keen sarcasm. Without you there would be nobody to keep Slashbots in check.

    6. Re:Singularity... by apankrat · · Score: 1

      "Because when we blue screen, all of your data goes down into a black hole."

      Shouldn't they use black screen instead ?

      --
      3.243F6A8885A308D313
    7. Re:Singularity... by jZnat · · Score: 1

      Black holes are usually pretty bright due to the masses near the even horizon accelerating at near-light speeds right into the deformed surface thingy (not really an actual surface, seems to be more like a super-dense cloud of a fat man's bowel movements) and releasing Hawking radiation.  Yeah, black holes are more white than black, damn racism.

      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
    8. Re:Singularity... by dtfinch · · Score: 1

      AFAIK, the most direct descendant of the old Microsoft XENIX is SCO OpenServer.

    9. Re:Singularity... by The_Dougster · · Score: 1
      When I was back in HS, I actually worked briefly for a guy who was running a Xenix sweatshop. He was hiring kids to hack out C code for Xenix on a TRS-80 Model II. This must have been around 1984 or so.

      Back then I could program in BASIC, but had no exposure to C prior to that. I lasted about a week before I admitted to myself that I had no fscking idea what was going on there.

      --
      Clickety Click ...
    10. Re:Singularity... by rendym · · Score: 1

      i love this joke...

      --
      Rendy Maulana
  6. singularity by technicolor.cavalry · · Score: 3, Funny

    so this one is going to be *so bad* that it's impossible to predict what will happen after its release?

    1. Re:singularity by Anonymous Coward · · Score: 0

      Wanna bet?

    2. Re:singularity by Varun+Soundararajan · · Score: 1

      No, we should interpret it this way:
      It took M$ this much time to understand that Windows sucks and need to get a better one running.
      ====
      This space is now not blank :)

  7. My guess: by autopr0n · · Score: 0

    It'll be slow as fuck.

    Actualy, this isn't that big of a deal, probably just a research project. OS's are not that hard to get started on

    Now, to bring it up to the level of OSX or Linux, that would be impresive.

    --
    autopr0n is like, down and stuff.
    1. Re:My guess: by Anonymous Coward · · Score: 1, Insightful
      Now, to bring it up to the level of ... Linux

      You're not even trying to make sense anymore, are you?

    2. Re:My guess: by zootm · · Score: 4, Interesting

      If you read the paper, the idea is that, yes, it'll be slower, but the reliability will be built in from the beginning, rather than other systems which take something fast and bolt reliability on. They make a good point that they will be able to use optimising compilers for CLR languages in this context, too.

    3. Re:My guess: by Anonymous Coward · · Score: 0

      This actually came up on Lambda the Ultimate and I RTFA when I saw it there.

      They actually do address performance in the whitepaper I read. They claim comparable performance to normal operating systems in micro benchmarks. The only real benchmark they have is a web server scenario where they are 'slow as fuck' but they blame that on a filesystem that only has 2.7Mb/s throughput (has the same performance on Windows).

      I found the state machine language extensions to c# to be rather interesting. Unfortunately I have no desire to program in a language as low level as sing#, but I don't have the understanding that would let me know if something like IronPython could work/run and ORMs could work. I like my reflection, dammit.

    4. Re:My guess: by l3v1 · · Score: 1

      It'll be slow as fuck.

      Well, sometimes slow is good :P

      --
      I am putting myself to the fullest possible use, which is all I can think that any conscious entity can ever hope to do.
    5. Re:My guess: by Anonymous Coward · · Score: 0

      One major flawed concept here is that the language can enforce safety for an operating system. That is, the written OS does provide some protection mechanisms but one of the fundamental ideas is that the C# variant they use will not allow people to write unsafe code. This works in an environment where all developers are trusted, but fails on the Internet where there are malicious software developers who could handcraft C#-ish programs with specific errors to induce escalation of rights.

      On a side note, the performance numbers were interesting. They compared their special compiler linked to their rather large environment to do "Hello, World" to a program statically linked to freeware environments. I do not have FC4 laying around, but my FC2 system with debugging and a static link could not get "Hello, World" above 400K. Drop the debugging and link dynamically to glibc and the same FC2 system is under 3K. Switching over to C++ and I can get a 1M static build with debug (stripped version is near their numbers). But again, the dynamic version is about 4K.

  8. MS-DOS 7.0 by simetra · · Score: 2, Funny
    Yeah baby!

    --

    "Would it kill you to put down the toilet seat?" -- Maya Angelou
    1. Re:MS-DOS 7.0 by Rude+Turnip · · Score: 1

      Wasn't that PC-DOS 7.0? Or was that developed independently of MS? I always thought that IBM simply rebranded MS-DOS to PC-DOS.

    2. Re:MS-DOS 7.0 by WMD_88 · · Score: 2, Informative
      MS-DOS 7.0, is, officially, Windows 95.

      Sorry, try again.

    3. Re:MS-DOS 7.0 by kaellinn18 · · Score: 1

      You can do iiiiiiiiiiiiiiiiit!! /Geico

      --

      --------
      This isn't the sig you're looking for. Move along.
  9. Like a Black hole? by Anonymous Coward · · Score: 4, Funny

    So, a new OS that can distroy all data AND matter.

    So much more advanced than a BSOD.

    1. Re:Like a Black hole? by Anonymous Coward · · Score: 0

      Or just a lot less metaphorical.

      For anyone that doesn't get it, it's not like the standard of the average Slashdot poster has been going up lately....

      Or maybe the BSOD will actually kill you this time.

  10. Reliability he says... by Iriel · · Score: 1, Redundant

    "We're sorry -- you have reached this page because a web server error occurred."
    They're talking about reliability and yet it looks like we already sladotted the page.
    Somehow, this leaves me wanting more</toungeincheek>

    --
    Perfecting Discordia
    www.stevenvansickle.com
    1. Re:Reliability he says... by BronxBomber · · Score: 2, Insightful

      Right. And /. has never taken down an Apache site. Mod me down, you haughty assholes. At least I've got the sack to post this using my real UN

      --
      ...both interiorlly, and exteriorlly.
    2. Re:Reliability he says... by Iriel · · Score: 1

      You obviously didn't see my closing tag. It was actually a joke.

      Slashdot has blasted many a site off the map before, but some have survived. I'm just saying it's funny that they post something about a new system built on reliability when it was already wanged before I was even able to comment. One would think Microsoft would have the guns to handle /.ers by now.

      --
      Perfecting Discordia
      www.stevenvansickle.com
    3. Re:Reliability he says... by Anonymous Coward · · Score: 0

      www.microsoft.com would... why on earth would they make research.microsoft.com able to handle all the traffic? It's on its own server... which I doubt see's large amounts of traffic ever.

    4. Re:Reliability he says... by BronxBomber · · Score: 0, Offtopic
      Meh, looks like I did, but frankly I have grown weary of the so called mighty /. ep33ns lately. It seems to be worse than usual, especially those of the AC variety.

      I also do not like the fact that my karma is so high. I am much more comfortably knowing that at least one person out there hates me.

      --
      ...both interiorlly, and exteriorlly.
    5. Re:Reliability he says... by rk · · Score: 1

      I'll mark you as a foe, if that makes you feel better... :-)

    6. Re:Reliability he says... by fymidos · · Score: 1

      it has, and it has been pointed just the same. Should we *not* point out that a site is slashdotted when it's a microsoft site ?!?!?!?

      --
      Washington bullets will simply be known as the "Bulle
    7. Re:Reliability he says... by peculiarmethod · · Score: 1

      You obviously didn't see my closing tag. It was actually a joke.

      The closing tag was ignored, as there was no opening tag.

      --
      ** "It's not my job to stand between the people talking to me, and the ones listening to me." -- Pego the Jerk
    8. Re:Reliability he says... by |/|/||| · · Score: 1

      When the data is parsed by humans, you can sometimes leave out the opening tag to build suspense and/or humor.
      </smarm>

      --
      [javac] 100 errors
  11. Dependability .... by Anonymous Coward · · Score: 0

    ... and Microsoft ?? Thats funny !!

    Btw ...also FP !!

  12. /.'ed by wiggles · · Score: 4, Funny

    Reliability, eh? Obviously, their web server isn't based on this OS.

    1. Re:/.'ed by ari_j · · Score: 0

      Focusing on dependability instead of performance - in other words, Singularity will be as dependable as ME is fast, at the expense of running slower than ME.

    2. Re:/.'ed by Anonymous Coward · · Score: 0

      Sure it is. It's just another Internet Ap--

      Oh, it's Novemeber 3? Not April 1?

      Oh.

      Nevermind.

  13. Singulary = Black Hole? by electricsalmon · · Score: 0, Redundant

    I find some irony in the name.... will this OS be a black hole that sucks everything (and everyone) into it?

    1. Re:Singulary = Black Hole? by Master+of+Transhuman · · Score: 1


      And how would that be different from every other OS Microsoft has ever released?

      They're all money sinks into Bill's pocket. They have no other purpose, let alone trying to extend the state of computer science or IT productivity.

      --
      Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
    2. Re:Singulary = Black Hole? by magarity · · Score: 1

      They're all money sinks into Bill's pocket
       
      There's no need to be bitter; You too can get in on the action with an Ameritrade account at $26.44 per share for MSFT plus a transaction fee.
       
      PS - No guarantees on ever having another dividend payout like once a while back.

  14. Imply... by wpiman · · Score: 1
    Do this imply that XP and current version of Windows are intended to be fast?

    Man- XP boots fast but that is about all.

  15. can pigs fly? by Anonymous Coward · · Score: 0

    Looking at how much time it took Vista to fly, i just hope this OS gets released before the next decade

    1. Re:can pigs fly? by ZeroExistenZ · · Score: 1

      You're being way too optimistic.

      --
      I think we can keep recursing like this until someone returns 1
    2. Re:can pigs fly? by PGC · · Score: 1

      And they , just as with Vista, probably will have to ditch some features. Dependability being the first one ...

      --
      The Dutch will inherit the earth. If not, we'll settle for a bit of ocean. Beta delenda est!
  16. our plan worked... by paul185 · · Score: 1

    ... Microsoft's research site is already slashdotted

  17. Server Error in '/' by jpsowin · · Score: 3, Funny
    Server Error in '/' Application.

    Runtime Error


    Wow, that page came up pretty fast. I guess their web server is built for performance instead of dependability.
    1. Re:Server Error in '/' by Anonymous Coward · · Score: 0

      No, we just collapsed the Singularity.

    2. Re:Server Error in '/' by abradsn · · Score: 1

      This is actually really cool stuff. Here is the pdf. Hopefully the ftp server is still up. ftp://ftp.research.microsoft.com/pub/tr/TR-2005-13 5.pdf

    3. Re:Server Error in '/' by aminorex · · Score: 1

      Farm of 8 mod_php web servers: $9600
      Arp-table based linux load balancer: $800
      Posting an ASP link on slashdot.... priceless

      There are some things money just can't buy.

      --
      -I like my women like I like my tea: green-
    4. Re:Server Error in '/' by CanadaDave · · Score: 1

      Haha, I saw that too when I tried the link. I thought for second there that it was April Fool's Day.

  18. Server Error in '/' Application. by Anonymous Coward · · Score: 0

    Clearly, their webserver is currently running Singularity.

  19. the finished products codename by know1 · · Score: 0

    "we (fucking) killed linux XP" {based on linu^W^W^W Microsoft technology

  20. Microsoft slashdotted? by P0ldy · · Score: 1

    Their depandable servers obviously aren't running Singularity. ;)

  21. Except that by Pike · · Score: 2, Interesting

    except that this implies that their other OSs emphasized performance over dependability.

    1. Re:Except that by Exocrist · · Score: 1

      wouldn't something need to be dependable to perform well?

    2. Re:Except that by Anonymous Coward · · Score: 0

      Technically no it wouldn't need to be.

      For instance, if the OS would run everything 2x as fast compared to any other OS, but would be prone to crashing often, it would have the best performance. In other words it is like overclocking, reduced stability/dependability/durability/reliability all for more performance.

  22. Hmmm..... by 8127972 · · Score: 1

    ".....designed new from the ground up, built on a new language and designed with emphasis on dependability instead of performance."

    How about security? God knows their OS'es need some.

    --
    This is my opinion. To make sure you don't steal it, it's covered by the DMCA.
  23. Slashdotted in six comments. by Tackhead · · Score: 4, Funny
    > We're sorry -- you have reached this page because a web server error occurred. There are many possible causes for this type of error, so we can't be more specific.

    Current setup was slashdotted within six comments.

    Future setup will place an "emphasis on dependability instead of performance".

    I'd say it sucks galactic black holes through buckytube, but that still wouldn't approach the Singular suckitude we're looking for.

    Bite my dimly red-shifted neutronium ass.

    1. Re:Slashdotted in six comments. by Entrope · · Score: 2, Insightful

      Premature optimization is the root of all blah blah blah. The web server isn't be running on Singularity anyway. OpenBSD shares a similar (albeit more human than mechanical) focus on correctness over performance, but nobody seems to think it is doomed to failure because of that.

      I think "Singularity" is not worth a hill of beans, but mostly because its novel ideas have already been tried and made little headway. Java systems have applied similar approaches to securing multiple processes within an address space in the past; microkernels have applied similar approaches to communications between processes. To the best of my knowledge, neither have resulted in software that is used outside of the initially targeted niche. Singularity mostly looks like the application of those previously tried approaches to a Microsoft virtual machine.

    2. Re:Slashdotted in six comments. by Master+of+Transhuman · · Score: 1

      "There are many possible causes for this type of error, so we can't be more specific."

      Because, like every other piece of software on the planet, we can't be bothered to actually keep track of what's going on in the program so we could tell you what the cause was. You'll notice our "new language" can't do that, either.

      Besides, we like issuing stupid error messages like every other Geek Moron(TM). Communication is not our strong suit.

      Besides, it would cost Bill money to do that - and that's not allowed around here.

      --
      Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
    3. Re:Slashdotted in six comments. by sharkey · · Score: 1
      I'd say it sucks galactic black holes through buckytube, but that still wouldn't approach the Singular suckitude we're looking for.

      You spelled 'Cingular' wrong there, buckaroo.

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
    4. Re:Slashdotted in six comments. by dhasenan · · Score: 1

      Perhaps true, but Microsoft has the capital to make it work. And if it provides the basis for the next major revision of Windows, so much the better.

      The trouble is, of course, compatability.

    5. Re:Slashdotted in six comments. by multi+io · · Score: 1
      OpenBSD shares a similar (albeit more human than mechanical) focus on correctness over performance, but nobody seems to think it is doomed to failure because of that.

      I do.

  24. New UI? by Pinback · · Score: 5, Funny

    Will the user interface be called Event Horizon?

    1. Re:New UI? by carlmenezes · · Score: 1

      yeah and the service packs will start with the name Andromeda :)

      --
      Find a job you like and you will never work a day in your life.
    2. Re:New UI? by GungaDan · · Score: 1

      Or voiced by Roddy McDowall?

      --
      Eloi are stupid, throw morlocks at them!
    3. Re:New UI? by rmjohnso · · Score: 1

      Gives new meaning to "compressing" a file.

      Oh crap, I just compressed it out of this space-time continuum.

      --
      "Extremism in the pursuit of liberty is no vice. Moderation in the pursuit of justice is no virtue." --Barry Goldwater
    4. Re:New UI? by blincoln · · Score: 1

      Will the user interface be called Event Horizon?

      So, in other words, the first adopters of Singularity will find themselves in an unfamiliar, empty, and slightly unsettling environment which vaguely reminds them of 2001, H.R. Giger, and - inexplicably for an operating system - a cathedral. They will attempt to get the system up and running like their standard OS, but most of them will be slaughtered in a variety of gory ways when the new Sam Neil Clippy-replacement finds their ISO of Hellraiser and identifies with Pinhead a little too much. The two survivors will delete the Singularity partition, only to discover that Sam (who was much better as Merlin) has made his way into their primary OS.

      Better than 2003 Server SP1 at least.

      --
      "...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
    5. Re:New UI? by Subrafta · · Score: 1

      Bluecurve?

      --
      Vuja De: That sinking feeling that this is going to happen again. Often occurs in meetings with Product Managers.
  25. This just in MS sucks...already Slash Dotted by haplo21112 · · Score: 0, Troll

    Only 18 comments in and the links are already slashdotted...

    Just goes to show what IIS and SQL Server will do for you....

    --
    Power Corrupts,Absolute Power Corrupts Absolutely, leaving one person(group)in charge is absolutely corrupt.
    1. Re:This just in MS sucks...already Slash Dotted by gstoddart · · Score: 1
      Only 18 comments in and the links are already slashdotted...

      Just goes to show what IIS and SQL Server will do for you....

      Or, that despite notions to the contrary, a lot of Slashdot readers actually read the stories.

      Posters and submitters might be a different situation though. :-P
      --
      Lost at C:>. Found at C.
    2. Re:This just in MS sucks...already Slash Dotted by Anonymous Coward · · Score: 0

      because only IIS + SQL server can be slashdotted ???

    3. Re:This just in MS sucks...already Slash Dotted by EraserMouseMan · · Score: 2, Insightful

      Yea, we've never seen a LAMP site /.ed now have we?
      So when /.ers kill a LAMP site do you post with the subject, "This just in LAMP sucks . . . already Slash Dotted"?

    4. Re:This just in MS sucks...already Slash Dotted by The+Bungi · · Score: 4, Insightful
      Just goes to show what IIS and SQL Server will do for you....

      Wow, and the last time I saw a /.'ed site spewing MySQL and Apache errors I thought it was just me. Because, well, I've heard that using open source will automagically upgrade your DSL to a T3. Free!

      Moron.

    5. Re:This just in MS sucks...already Slash Dotted by haplo21112 · · Score: 1

      Not saying that at all, I just expect a company like microsoft to have infrastructure that can stand up to a slashdotting better than most.

      --
      Power Corrupts,Absolute Power Corrupts Absolutely, leaving one person(group)in charge is absolutely corrupt.
    6. Re:This just in MS sucks...already Slash Dotted by haplo21112 · · Score: 1

      Again one would expect that Microsoft would have the infrastructure to survive the massive traffic surge of a slashdotting, better than this...

      --
      Power Corrupts,Absolute Power Corrupts Absolutely, leaving one person(group)in charge is absolutely corrupt.
    7. Re:This just in MS sucks...already Slash Dotted by The+Bungi · · Score: 1

      Microsoft Research. Quite a different thing.

    8. Re:This just in MS sucks...already Slash Dotted by Anonymous Coward · · Score: 0

      Still the same money!

      At least we know what their next project is: Project Dotty. A webserver that can survive /. .

    9. Re:This just in MS sucks...already Slash Dotted by jose+parinas · · Score: 1

      Can you tell me if was the MS link the /.ed one? Because the second link is on my site with Linux Centos, in this case is a blog site, and not tunned to a huge traffic, I want to improve my site, so you information will be valuable for me.

    10. Re:This just in MS sucks...already Slash Dotted by EraserMouseMan · · Score: 1

      Hi, It was the top link. "Singularity" I didn't click on the bottom link. I'm glad that to see that you are doing what you can to improve performance of your site though! I've developed some free public sites that have huge surges in activity on occasion too. So I'm familiar with what you're feeling. Best of luck to ya!

    11. Re:This just in MS sucks...already Slash Dotted by jose+parinas · · Score: 1

      Thanks, I just want to be prepared in case of being /.ed :). I think that CentOS could do the job as expected.

  26. right on! by isotope23 · · Score: 1, Funny

    wholly new operating system under development called Singularity,

    appropriate name, as the gravitational pull of bloated code will cause
    the OS to implode into the black screen of death....

    --
    Service guarantees Citizenship! Questions Guarantee GITMO.... Amerika Uber Alles!
  27. At last, an honest ship date! by n6mod · · Score: 2, Funny

    Glad to see they're sticking with their naming convention... This just confirms that it will take MS until the end of time to ship a stable OS.

    --
    You have violated Robot's Rules of Order and will be asked to leave the future immediately.
    1. Re:At last, an honest ship date! by Dirtside · · Score: 2, Funny
      This just confirms that it will take MS until the end of time to ship a stable OS.
      Well, duh. What do you think Milliways runs on its terminals?
      --
      "Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
    2. Re:At last, an honest ship date! by WilliamSChips · · Score: 1

      And "making Windows stable" is one of the many impossible things Milliway's does...

      --
      Please, for the good of Humanity, vote Obama.
  28. Well.... by Petaris · · Score: 2, Insightful

    Quote:
            "designed with emphasis on dependability instead of performance."

    Well since there goal has always been to have both dependability and preformance and they never succeded I suppose it is rather wise for them to cut back on the complexity and just try to get one of them.

    --
    ~Petaris "The world is open. Are you?"
  29. Service Unavailable by rbanffy · · Score: 0, Redundant

    It seems http://research.microsoft.com/os/singularity/ collapsed into a singularity due to overwhelming /. traffic...

  30. Slashdotted by mystic_mushroom · · Score: 1

    I hope the website isn't a testament to the dependability of the new OS...

  31. code name by Anonymous Coward · · Score: 0

    Windows 3K, aka Wingoogle

  32. marketing stunt by Anonymous Coward · · Score: 0

    The whole point of Singularity is to imply XP is flaky 'cos it's such a hot rod?

  33. In other news... by Lendrick · · Score: 5, Funny

    Last week, the latest build of Windows Vista became so horrendously bloated that it underwent gravitational collapse... coincidence?

    1. Re:In other news... by Anonymous Coward · · Score: 0

      ...and took OpenOffice.org with it.

    2. Re:In other news... by Anonymous Coward · · Score: 0

      Last week, the latest build of Windows Vista became so horrendously bloated that it underwent gravitational collapse... coincidence?
      - Nah, someone installed the latest Sony rootkit on Vista.

  34. Text from the second link by Anonymous Coward · · Score: 2, Insightful

    anonymous so as not to whore karma:

    One interesting concept is the abstraction of Software Isolated Processes (SIPs).

    SIPs provide the strong isolation guarantees of OS processes (isolated object space, separate GCs, separate runtimes) without the overhead of hardware-enforced protection domains. In the current Singularity prototype SIPs are extremely cheap; they run in ring 0 in the kernel's address space. Singularity uses these advances to build more reliable systems and applications. For example, because SIPs are so cheap to create and enforce, Singularity runs each program, device driver, or system extension in its own SIP. SIPs are not allowed to share memory or modify their own code. As a result, we can make strong reliability guarantees about the code running in a SIP. We can verify much broader properties about a SIP at compile or install time than can be done for code running in traditional OS processes. Boarder application of static verification is critical to predicting system behavior and providing users with strong guarantees about reliability"
    Source: Singularity Site

    From the report we can read that:

    SIPs are the OS processes on Singularity. All code outside the kernel executes in a SIP.
    differ from conventional operating system processes in a number of ways:

    SIPs are closed object spaces, not address spaces. Two Singularity processes cannot
    simultaneously access an object. Communications between processes transfers exclusive
    ownership of data.

    SIPs are closed code spaces. A process cannot dynamically load or generate code.
    SIPs do not rely on memory management hardware for isolation. Multiple SIPs can reside
    in a physical or virtual address space.

    Communications between SIPs is through bidirectional, strongly typed, higher-order
    channels. A channel specifies its communications protocol as well as the values
    transferred, and both aspects are verified.

    SIPs are inexpensive to create and communication between SIPs incurs low overhead.
    Low cost makes it practical to use SIPs as a fine-grain isolation and extension
    mechanism.

    SIPs are created and terminated by the operating system, so that on termination, a SIP's
    resources can be efficiently reclaimed.

    SIPs executed independently, even to the extent of having different data layouts, run-time
    systems, and garbage collectors.

    1. Re:Text from the second link by bersl2 · · Score: 1

      SIPs provide the strong isolation guarantees of OS processes (isolated object space, separate GCs, separate runtimes) without the overhead of hardware-enforced protection domains. In the current Singularity prototype SIPs are extremely cheap; they run in ring 0 in the kernel's address space.

      Would somebody care to explain why the two emphasized statements are not (nearly) mutually-exclusive? Or is security not included in the concept of stability? Or is there some restriction even on ring 0 that I am ignorant about?

    2. Re:Text from the second link by twiddlingbits · · Score: 1

      Wow, flamebait mod for telling the truth!!! Yes, these were around on mainframes in the 1970/80s and as well as being in DEC VMS as well. As usual, M$ re-invents (or copies) other's work and claims it is new.

    3. Re:Text from the second link by rewt66 · · Score: 1
      I think it's because of the text you didn't bold: "without the overhead of hardware-enforced protection domains."

      So here's what I think is going on: They create these separate "spaces". Each space is a separate .Net virtual machine (yeah, that sounds like it's low-overhead to create), and therefore has its own GC. Each has its own separate runtime, because that's what was loaded into the .Net virtual machine. But all these VMs are running in ring 0, and are only protected from each other by the VM's restrictions, not by any hardware (or even kernel!) mechanisms.

      Conclusion: If one of the "spaces" has unmanaged code, that unmanaged code can stomp all over the other spaces.

      That's my interpretation, anyway...

    4. Re:Text from the second link by shmlco · · Score: 1
      I'm sick and tired of all the idiots here who can do little more than bash someone else just to reinforce their own delusions of superiority. "Master of Transhuman", indeed.

      Okay, "master." Show me a 1970's era "module" that has ALL of the characteristics of the SIPs listed above...

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    5. Re:Text from the second link by Wesley+Felter · · Score: 1

      A SIP is like a Java/.NET sandbox. Because every SIP runs in a sandbox, hardware protection is not needed.

    6. Re:Text from the second link by Anonymous Coward · · Score: 0

      Lets take these one at a time..

      Two Singularity processes cannot simultaneously access an object.

                                  Nothing new, that's a semaphore.

      Communications between processes transfers exclusive ownership of data.

                                      Nothing new, that's data locking. It's been in databases for years.

      SIPs are closed code spaces. A process cannot dynamically load or generate code.

                                      OK, thats nothing new either. You really shouldn't do this anyway.

      SIPs do not rely on memory management hardware for isolation. Multiple SIPs can reside
      in a physical or virtual address space.

                                        Sounds like a BIG area for bugs, you got to control the addresss space somehow. I
                                        wouldn't trust my OS to do memory address verification on each access. Talk about
                                        SLOW. People were complaining on /. yesterday memory access is too slow.

      Communications between SIPs is through bidirectional, strongly typed, higher-order
      channels.
                                            JMS anyone?

      A channel specifies its communications protocol as well as the values transferred, and both aspects are verified.
                                              MQ Series does this. Nothing new.

      SIPs are inexpensive to create and communication between SIPs incurs low overhead.
      Low cost makes it practical to use SIPs as a fine-grain isolation and extension
      mechanism.

                                            Any process is pretty cheap to create. Low Overhead comm, using the comm process
                                            as described above..not likely. Bogus claim. Cost has nothing to do with isolation
                                            and extension.

      SIPs are created and terminated by the operating system, so that on termination, a SIP's
      resources can be efficiently reclaimed.

                                                OK, nothing new here. That's done all day long in modern OSes.

      SIPs executed independently, even to the extent of having different data layouts, run-time
      systems, and garbage collectors.

                                                  Nothing new, even the run-time systems. That is like an OS running on an OS, or
                                                  virtualization or emulation.

      I can't see what all the fuss is about. They haven't invented anything new.

    7. Re:Text from the second link by Master+of+Transhuman · · Score: 0


      Show me a SIP with any of the characteristics listed.

      As far as I can see from the quote, this is just vaporware talk. I can't see any difference between this stuff and the original ideas of software modularization, information hiding, coupling, and the rest of the structured programming concepts from the 1970's, let alone OOP. The only distinction is that they appear to be talking about the runtime characteristics, instead of the source code.

      They talk about "communicating on a higher channel" - what the hell is that if not decomposition in 1970's speak? The upper levels of the system control the system flow, the lower levels do one thing and one thing only, being called and passed only that data they need to do their job.

      I don't see a single thing new there. "Closed address spaces"? Nothing can talk to each other? Sounds the opposite of what a software system needs to me.

      To be charitable, perhaps they're referring to the notion of a fixed OS that doesn't change and is so totally sandboxed, even internally, that the introduction of errors is difficult.

      So what? This is new? Maybe new to Microsoft, when Allchin has admitted recently that they do nothing but spaghetti code which is why Vista wouldn't ever work until they redesigned their coding methods, but I suspect most OS designers aim for these characteristics. Achieving them and still having an OS that can adapt and change is the problem.

      But adapting and changing and getting better is not something Bill cares about - unless it puts money in his pocket.

      --
      Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  35. Dependability? by Anonymous Coward · · Score: 0

    Sorry, alraedy have it...it's called WinXP Prof. Service Pack 2.

  36. Dependability would be good by Anonymous Coward · · Score: 0

    Server Error in '/' Application.

  37. In "math speak" singularity means... by StressGuy · · Score: 1

    something wierd happens here and we don't really know why.

    [paraphrasing of course, sure the math battallion will come in to clarify]

    Not the greatest marketing name I would think

    --
    A goal is a dream with a deadline
    1. Re:In "math speak" singularity means... by The_Dougster · · Score: 1
      something wierd happens here and we don't really know why.

      Well, if you do a root-locus plot of an oscillating function, you will get complex conjugate poles at points which correspond to the harmonic resonance frequency. The poles shoot up to infinity like a huge mountain sticking up out of the plane. There's nothing really mysterious about it.

      Singularities tend to imply some sort of harmonic resonance, at least in the mechanical realm.

      --
      Clickety Click ...
  38. Singularity... by Hymer · · Score: 1

    Single user, single threaded MS OS
    I suppose that this will be MS UNIX... a child of XP and Xenix...

  39. *instead* of performance? by Anonymous Coward · · Score: 0

    Yeah, so it will never crash but will load in 24134 years

  40. Google cache by sachu · · Score: 2, Interesting
  41. release date... by alexandreracine · · Score: 0

    Actually it will be impossible to predict a precice relase date in the first place! :)

    --
    No sig for now.
    1. Re:release date... by Master+of+Transhuman · · Score: 1


      How is that different from every other OS Microsoft has ever released?

      --
      Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  42. Benefit of the Doubt by ndansmith · · Score: 0, Troll
    Is anyone at all excited about this possibility? I am.

    Microsoft's OSs have bloated and become bogged down, just piling each new generation on top of the heap. This provides a chance for Microsoft to flex its development muscle (i.e. money) to get something done, free from the constraints of history. Imagine a world without the registry and .DLLs! Imagine a world where Windows is based on a functional command prompt!

    Of course, this would really suck for all those developers who have fine-tuned their software to Windows madness only to have it all exploded a few years down the line.

    Still, I am going to give MS the benefit of the doubt on this one. Of course, since it is still vaporware, there is much doubt, and therefore much benefit. We'll see what happens when the fog clears . . .

    1. Re:Benefit of the Doubt by xtal · · Score: 1


      Of course, this would really suck for all those developers who have fine-tuned their software to Windows madness only to have it all exploded a few years down the line.


      Perhaps that would be a valuable lesson about developing your software to a propietary, closed API, wouldn't it?

      I'm not sure what would be gained from doing this, as opposed to doing what Apple did, and put a slick user interface onto a decades-tested BSD core.

      --
      ..don't panic
    2. Re:Benefit of the Doubt by zootm · · Score: 1

      It's a different approach to writing OSs in general. BSD is dependable (when built right) because it's been around for a long time. This system is aiming to abstract everything so that sources of instability just can't happen. Everything is abstracted to an object model, it's similar to a system running in a Virtual Machine, but "not really".

      As for developing to proprietary APIs, this system appears to be built upon CLR, which is an open specification.

    3. Re:Benefit of the Doubt by jcr · · Score: 1

      This provides a chance for Microsoft to flex its development muscle (i.e. money) to get something done, free from the constraints of history.

      They tried it once before. Remember OS/2?

      MS's customers are all about inertia. This effort is doomed, whether the software's any good or not.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    4. Re:Benefit of the Doubt by Anonymous Coward · · Score: 0

      What fucking retards modded this guy a troll? "Oh he's not some brainwashed BSD/Linux/GNU weenie and he's stating his opinion in a mature and non-vitriolic manner! HOW DARE HE!!!!"

  43. Lack of Dynamic Loading by ChefInnocent · · Score: 1

    I read through some of the "merits", and I have serious issues with the lack of DLLs. DLLs have become my patron saint of programming, and this thing wants to get rid of that. I'm not even sure MS could really continue if they got rid of DLLs. There may be other problems with their idea, but this is the first the leapt out at me.

    1. Re:Lack of Dynamic Loading by Wesley+Felter · · Score: 1

      My understanding is that Singularity supports DLLs, but they must be loaded when a process starts. If you need to load new code while a process is running, just spawn a new process and communicate with it.

    2. Re:Lack of Dynamic Loading by zootm · · Score: 5, Informative

      A quote from Galen Hunt (apparently someone working on it) from the Channel9 video page (I have to say I've not watched the video, at least yet, it's just interesting wherever developers actually reply to queries), says something about this:

      In Singularity, you can add new code to your application. However, instead of loading it into your own process, you load it into a child process. The OS facilitiates setting up channels between the child and its parent.

      While this is still very much a work in progress, the results so far look promising. For example, we have a dynamic web server that uses child processes. Also all of our device drivers run in child processes.

      I don't know if that directly answers your question, but I think it kinda explains how they're dealing with this sort of thing.

    3. Re:Lack of Dynamic Loading by Anonymous Coward · · Score: 0

      Wow, a web server that uses child processes. I am in awe of this radical new technology.

    4. Re:Lack of Dynamic Loading by Anonymous Coward · · Score: 0

      Thank's for the proof of concept. So, is this new OS running on MS paper?

    5. Re:Lack of Dynamic Loading by ChefInnocent · · Score: 1

      Actually, both yours and Wesley's answered the question quite sufficiently. Thanks.

  44. singularity on MS' channel 9 vlog by lopati · · Score: 4, Informative

    here's jim larus and galen hunt talking about their project.

  45. I hacked on this... by megabeck42 · · Score: 5, Interesting

    I saw and worked on this a bit while interning at Microsoft. Although what I say is my own and doesn't reflect Microsoft in any way, it's important to remember that this is a research operating system, so its not challenging or replacing Windows. They have some very good, solid ideas. I hope that, someday, it will be released.

    --
    fnord.
    1. Re:I hacked on this... by zootm · · Score: 1

      Thanks for being one of the two posts on this topic that isn't "HAHAHAHA their server fell over!" or "Dependable? You mean like Linux?". I had thought that the differences with this system would be obvious.

    2. Re:I hacked on this... by LifesABeach · · Score: 1

      You've got to ask yourself, "Why would a world wide corperation create a new product when they've made Billions, (with a "B"), on the old one?"

    3. Re:I hacked on this... by Moofie · · Score: 1

      Well, gee, with specific details like that, how could they possibly fail!? Thanks for sharing, Microsoft Intern Guy!

      --
      Why yes, I AM a rocket scientist!
  46. It was designed for performance? by MECC · · Score: 2, Funny

    Wow.

    --
    "We are all geniuses when we dream"
    - E.M. Cioran
  47. I'm disappointed in you, Slashdot by Anonymous Coward · · Score: 1, Insightful

    Nothing but redundant posts and tired cliches for comments on this article so far. But being critiques of Microsoft the mods will be retarded enough to mod it all Funny/Insightful/blah/blah/blah instead of Redundant and Overrated that they deserve.

    Slashdot's credibility as a serious news site went through a black hole for all it's worth.

    1. Re:I'm disappointed in you, Slashdot by Widowwolf · · Score: 1

      You just mad that you have nothing original to say?

      --
      ~~"Of course, that's just my opinion. I could be wrong." ~~Dennis Miller
    2. Re:I'm disappointed in you, Slashdot by Anonymous Coward · · Score: 0

      D000d like totally. Remember -- MICRO$OFT $UCKS LOL. Gotta have the dollar sign in there because they're a corporation and Amerikkkan right?

  48. They appear to be running it now by Anonymous Coward · · Score: 0

    When going to the link, I get "service unavailable". Apparently, they are not able to handle a little /.

  49. Features? by smittyoneeach · · Score: 1, Troll

    Likely it will by default hide entire file names, and not merely the file extensions, for known types.
    Just wasted 10 minutes on that degenerate, perverted mis-feature.
    Props to /. for affording me an opportunity to share my enthusiasm for Redmond's non-command of OS design.

    --
    Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    1. Re:Features? by Anonymous Coward · · Score: 0

      Modded 2 Troll as of now. Go 5 Troll! Go 5 Troll! Make with the underrated mods!

    2. Re:Features? by NullProg · · Score: 1

      Dude, you got mis-modded. +2 Troll? I think the Microsoft moderators are in charge today.

      Enjoy.

      --
      It's just the normal noises in here.
    3. Re:Features? by ozmanjusri · · Score: 1

      I think the Microsoft moderators are in charge today.

      It's actually sort of creepy reading at -1 at the moment. Anything not 100% enthusiastic about Microsoft is being modded troll.

      There's always been a lot of astroturfing here, but for some reason they're all crawling out from under their rocks today.

      --
      "I've got more toys than Teruhisa Kitahara."
    4. Re:Features? by kubevubin · · Score: 1

      How is it 'creepy'? I'd label it as 'surprising', personally, as I'm used to seeing any pro-Microsoft/Windows posters somehow being modded as trolls. While I never thought I'd see the day when Microsoft actually started building a new OS from the ground up, I must say that I have complete faith in them, seeing as how they obviously have a clearer vision of what they need to do in order to make things work.

    5. Re:Features? by ozmanjusri · · Score: 1

      How is it 'creepy'?

      Because large nombers of valid, interesting comments are being modded to oblivion because they don't support a particular vendor's product. The fact you don't see that as a bad thing speaks volumes for your own bias.

      I'd label it as 'surprising', personally, as I'm used to seeing any pro-Microsoft/Windows posters somehow being modded as trolls

      No, you're not used to that. You're saying it because it suits your purpose to pretend Microsoft is under attack here.

      I must say that I have complete faith in them

      Now that is just bizarre.

      --
      "I've got more toys than Teruhisa Kitahara."
  50. No it doesn't by Anonymous Coward · · Score: 0

    Windows XP pretends to boot quickly. Bascially it puts up a pretty picture of the gui right away, but you can't actually do anything.

  51. Define "innovation" in that context. by khasim · · Score: 0, Redundant
    microsoft *has* been responsible for some real innovation, and *does* have a few products that work really well. hell, singularity might even be cool.
    Such as what, specifically?

    Microsoft is great at waiting until other people have done the development and then buying them out/cloning their work and polishing it. Microsoft is really great at marketing their products. They got people to stand in the rain, at midnight, to buy an OS.

    But "innovation"? I don't see that.
    1. Re:Define "innovation" in that context. by zootm · · Score: 4, Insightful

      Try checking out the Microsoft Research page, and their past systems stemming from there. You might be surprised.

    2. Re:Define "innovation" in that context. by devilsadvoc8 · · Score: 4, Insightful

      The relentless bashing of Microsoft in this manner is tiring. Have they made flawed products? Absolutely, but to generalize their contribution to modern computing as nothing more than theft and good marketing is pure garbage. However such posts are good at karma whoring...

      --
      B O R I N G
    3. Re:Define "innovation" in that context. by be_kul · · Score: 1

      ok, let's try: In most latin words, the prefix "in-" is the sign of negation or opposition, e.g. "incompetence" is contrary to "competence". And "nova" obviously stands for "new" - so, "innovation" is the opposite of ...? ;-)

    4. Re:Define "innovation" in that context. by Overly+Critical+Guy · · Score: 1

      Their contribution to modern computing is to have ridden the wave of cheap commodity PCs that needed a GUI to run them. When I think of all the time and money that has been wasted keeping Windows systems from falling over themselves, I shake my head. People are now afraid of computers, paranoid of being on the Internet, and have been convinced that it's normal to require anti-virus and anti-spyware software as a layer between you and the applications you run.

      Can you really name a positive contribution they were on the forefront of making?

      --
      "Sufferin' succotash."
    5. Re:Define "innovation" in that context. by gatsu · · Score: 0
      They got people to stand in the rain, at midnight, to buy an OS.
      I thought that was Apple.
    6. Re:Define "innovation" in that context. by jcr · · Score: 2, Funny

      to generalize their contribution to modern computing as nothing more than theft and good marketing is pure garbage.

      Perhaps you can specify some of their alleged contributions?

      That's OK, we'll wait.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    7. Re:Define "innovation" in that context. by rpozz · · Score: 1

      Absolutely, but to generalize their contribution to modern computing as nothing more than theft and good marketing is pure garbage.

      Compare Microsoft's contributions to modern computing to those made by IBM, Sun, Apple, and SGI.

    8. Re:Define "innovation" in that context. by symbolic · · Score: 1

      From Microsoft's very inception the undercurrent has been driven by opportunism and a keen desire to take advantage of others.

    9. Re:Define "innovation" in that context. by NineNine · · Score: 1

      Microsoft is really great at marketing their products. They got people to stand in the rain, at midnight, to buy an OS.

      If that's the case, then what is Apple, omnipotent? Apple freaks stand in line, all night, seemingly every few months when the new Apple Gadget version x.x.x.x comes out. MS is good at marketing, but they're nothing comapred to Apple. MS is selling what is now a cheap, commodity OS. They come out with a new one every fewyears. Apple sells high priced, super-premium consumer OS, with a new full priced version every few months, and their customers STILL wait in line for it. On top of that, have you ever seen a MS tattoo? I've seen pictures of a bunch of Apple tattoos...

    10. Re:Define "innovation" in that context. by Anonymous Coward · · Score: 0

      Innovate: 1548, from L. innovatus, pp. of innovare "to renew or change," from in- "into" + novus "new."


      Sorry to spoil your joke. :)

    11. Re:Define "innovation" in that context. by drsquare · · Score: 1

      Without Microsoft we'd be paying £1000 for Macs just to send an e-mail, or fiddling with Linux command lines.

    12. Re:Define "innovation" in that context. by thelexx · · Score: 1

      "Absolutely, but to generalize their contribution to modern computing as nothing more than theft and good marketing is pure garbage."

      Fucking name one then.

      --
      "Gold still represents the ultimate form of payment in the world." - Alan Greenspan, 1999
    13. Re:Define "innovation" in that context. by rajafarian · · Score: 1

      When I think of all the time and money that has been wasted keeping Windows systems from falling over themselves...

      I think of the over $300,000 that I have made the last ten years doing so.

    14. Re:Define "innovation" in that context. by fitten · · Score: 1

      Yeah, they're so afraid of the Internet that growth has been doubling every year since around the Windows'95 release timeframe. They are paranoid about being on the 'net and think it's normal to run anti-whatever ware as a basic acceptance (whether right or wrong) that computers are not infallible. In some ways, computers have evolved from being "magic" and "universally fantastic" to being "just another device" that has its share of problems and issues just as any other product. I think this has been good, overall, for the world. Holding something as being "magic" by the general populace leads to some bad things (worship, etc.).

      Positive contribution my Microsoft: commoditized and standardized the personal computer products. An example of standardization is graphics cards (before Microsoft imposing standards, every card was different, etc.) Have you ever set up Glide? or had a game that ran against VESA (crappy) or Glide (proprietary but good)? The reason why graphics cards are like they are today is because of Microsoft. Derived from this is games on the PC. Software developers don't want to have to build against and test against several grahpics APIs. A standard graphics API has made making software (games) much easier to write to target a large market (all Windows PCs as opposed to PCs with Brand X or Y video cards). Commoditization of PCs can be seen in the fact that so many households around the world have PCs now.

      Do not underestimate what benefits having (practically) a single platform to code against has had on the software industry. Being able to write one piece of software and have it runnable by 90%+ of the world's machines is a very strong benefit.

      Not only this but Linux itself has benefitted. Not only did Microsoft give all those folks someone to hate (someone to motivate them) but the standardization and commoditization of PCs has directly enabled Linux to be successful. PCs are cheaper as well as have a number of features that Intel and Microsoft developed together.

    15. Re:Define "innovation" in that context. by stretch0611 · · Score: 2, Interesting

      Absolutely, but to generalize their contribution to modern computing as nothing more than theft and good marketing is pure garbage.

      Ok, that's your opinion. I however beleive that they have only copied and stolen products without any real innovation.

      Microsoft started by selling BASIC intepreters for the old Altair computers. However, their compilers were mainly based on public domain alternatives at the time. (Copy and/or stolen, not innovation)

      As we progress to the era of DOS, When M$ was approach by IBM, they said they had a CP/M clone (but didn't) and bought the rights to QDOS which they resold as their own. (Clone of CP/M which they bought)

      Further history of Microsoft reveals much more of the same.

      • Windows - Copy of the Mac's Gui which was stolen from Xerox PARC
      • Word - There were some many prior entrants I do not remember which was the first, but it wasn't M$. (unless maybe it was EDLIN which was horrendous to work with)
      • Excel - Clone of Lotus 1-2-3 which was a clone of Visicalc
      • Access - one of the first PC database I remember was dbase - but there was probably something earlier.
      • Money - This was only developed because a judge refuse to let M$ buy Quicken
      • Drivespace (Disk Compression) - wasn't around until after Stacker. (there was a big lawsuit on this one too! (Microsoft Lost)
      • Visio - This was written by a seperate company until M$ bought them in 2000.
      • Tablet PCs - Another lawsuit on this one a few years back because it is based on prior "Pen Computing"
      • Even M$ Bob, the OS flop which came back to haunt us as the stupid paperclip in M$ Office was a copy. I think it came from the avatar from the now defunct Sierra Network.
      • Internet Explorer, Recycle Bin/Undelete, Disk Defragmenter... - All are more examples of other people's ideas that Microsoft incorporated into the OS as their own.

      Microsoft is a monopoly and does not innovate. I have shown multiple examples of this. Microsoft will buy or copy things that are truly innovative and then try to rewrite history as if they were their own all of history.

      You have not given even one example of Microsoft innovation. When you do I may consider your post valid.

      --
      Looking for a job?
      Want your resume written professionally?
      DON'T USE TUNAREZ!!!
    16. Re:Define "innovation" in that context. by Overly+Critical+Guy · · Score: 1

      Software developers don't want to have to build against and test against several grahpics APIs. A standard graphics API has made making software (games) much easier to write to target a large market (all Windows PCs as opposed to PCs with Brand X or Y video cards).

      You write of Direct3D as though OpenGL didn't exist. Cheap, commodity PCs existed before Windows 95. Like I said, it's because of cheap, commodity PCs that Windows is everywhere, not the other way around.

      --
      "Sufferin' succotash."
    17. Re:Define "innovation" in that context. by Oriumpor · · Score: 1

      The previous anger displayed is certainly well justified, if a little one sided. Still, to downplay said frustrations is equally biased.

      What would be closer to accurate than either of these equally slanted statements would be something along the lines of the following:

      "Microsoft funds R&D programs which will, through one means or another, help to contribute to their stranglehold on the Desktop Market. Alternatively, some of these R&D programs eventually end in new concepts which increase usability in computing for all but on the whole most are rehashes of existing computing practices."

      Take a look at research.microsoft.com There are some genuinely interesting R&D projects in the hopper, as well as in the past. But as is pretty evident few things listed are/would be revolutionary.

    18. Re:Define "innovation" in that context. by Oriumpor · · Score: 1
    19. Re:Define "innovation" in that context. by protohiro1 · · Score: 1

      The "microsoft bashing" bashing is getting pretty bad on slashdot lately. I got modded troll for saying that Windows XP was basically shit. Which I guess is fair. But I still think it sucks. Microsoft really needs to tear that thing down and start over, so I think this sounds good to me. Windows NT was never intended to be what it is today. It was written as a single user desktop operating system. UNIX and friends were intended to be multi-user server operating systems, which coincidentaly is very useful on the desktop these days. Microsoft has done a commendable job bolting security, multiple users, real memory management, etc onto an os that wasn't designed with those things in mind. That said, at a certain point its never going to get better without starting from scratch.

      --
      Sig removed because it was obnoxious
    20. Re:Define "innovation" in that context. by jenglish · · Score: 1

      > Perhaps you can specify some of their alleged contributions?

      The combobox and the scroll wheel are the first things that come to mind. I'm sure there are more.

    21. Re:Define "innovation" in that context. by npsimons · · Score: 1

        . . . but to generalize their contribution to modern computing as nothing more than theft and good marketing is pure garbage.

      Really? And how, exactly, would you generalize their contribution to modern computing? Please, enlighten us, for all the evidence I have seen has pointed precisely to Microsoft being nothing more than thieves and marketers.
    22. Re:Define "innovation" in that context. by mingot · · Score: 1

      Um, most users of XP are not using it as a multiuser OS, so why should they "tear it down" and re-write it as one?

    23. Re:Define "innovation" in that context. by _Sprocket_ · · Score: 1

      Exactly. The parent poster obviously needs to read up a bit on microcomputing history. As an aside - I can't believe I'm agreeing with Overly Critical Guy on something. :P

      It might be worth noting that Microsoft did provide one of the key components that lead to the commodity computer market; an identical OS. MS DOS, the non-IBM licensed version of PC DOS, allowed those who were able to piece together the software and reverse engineer the BIOS an identical OS to IBM's systems and therefore exact compatability with IBM systems. And this is why Microsoft flourished - it rode the wave of the commodity hardware market.

      You gotta wonder... without QDOS... would CP/M have ended up providing that same key component to Compaq?

    24. Re:Define "innovation" in that context. by drsmithy · · Score: 1

      Their contribution to modern computing is to have ridden the wave of cheap commodity PCs that needed a GUI to run them.

      "Helped is the word your after. "Microsoft" and "cheap commodity PCs" have a symbiotic relationship. Both fed off the success of the other.

      People are now afraid of computers, paranoid of being on the Internet, and have been convinced that it's normal to require anti-virus and anti-spyware software as a layer between you and the applications you run.

      What's funny is that you think the situation would have been any different if MacOS, AmigaOS or anything else had captured 95% of the userbase.

      People are scared of trying to program their TVs, VCRs and Microwaves as well. You really think a PC without Windows on it would be any less intimidating ?

    25. Re:Define "innovation" in that context. by drsmithy · · Score: 1
      Ok, that's your opinion. I however beleive that they have only copied and stolen products without any real innovation.

      So, by your measure, who has innovated ? And how ?

      Microsoft is a monopoly and does not innovate. I have shown multiple examples of this.

      Who does ? How ? What's your definition of "innovation" ? It's impossible to have any sort of rational discussion on the topic without knowing where the goalposts are.

      Microsoft will buy or copy things that are truly innovative and then try to rewrite history as if they were their own all of history.

      Where do they do this ? Have you got any examples of Microsoft buying a product or technology and then trying to claim they did it all themselves ?

    26. Re:Define "innovation" in that context. by fitten · · Score: 1

      GL did exist and was partially supported by Glide, for example, in the early '90s. OpenGL was ratified in 1992 but took a while for adoption. Not even all the Un*x vendors adopted OpenGL quickly. The amount of support vendors offered even differed (both on Un*x machines and PC video cards). It was hardly a "standard" on the PC side of the coin and never really was *the* standard. A number of cards delivered OpenGL libraries for their cards and OpenGL came close to being *the* standard with the Voodoo cards but DirectX came out and for various reasons, DirectX pretty much won. On the PCs, you had lots of choices... CGA, EGA, VGA, VESA (hopefully only if that was your only option), and others, in addition to a few cards like the Voodoo Glide cards that supported only a subset of OpenGL and some other cards that supported their own proprietary APIs. Also, Microsoft/Windows was defining graphics cards standards during the Windows 3.1 timeframe, which was quite a bit of time before Windows 95 and a bit of time before PCs were really commodity items.

      The history of the PC and how it became a commodity is entertwined with Windows since Windows was delivered with PCs the whole time. Which caused which? I guess I'd have to think about it more.

    27. Re:Define "innovation" in that context. by _Sprocket_ · · Score: 1

      Commodity computing came about during the time of DOS - far, far before Windows.

    28. Re:Define "innovation" in that context. by fitten · · Score: 1

      It was there, somewhat, but not to what we know today.

      Take graphics cards, for example, I thought about this some last night. Before there was a "standard" API, they spent time on performance, price, their own API, and wooing developers (games and applications such as AutoCAD) to use their API. When Microsoft said "use our API and we'll handle the developers", that freed up the graphics companies to concentrate on performance and price (freeing up the companies from the kickbacks and such allowed prices to drop even more). Microsoft handled getting the developers (games and other applications) onto Windows.

      "Commodity computing came about during the time of DOS - far, far before Windows." Simply stating this over and over without definition does not make it true. Did you ever buy a DOS machine? I did... several, and they were not really commodity. Sure, they were mass produced but they were not cheap (which is the other side of the 'commodity' coin). The prices of the machines back there were roughly what they cost now. You could get a decent machine for $1200 or so (today, I'd say you could get a decent machine for $600 though), however, the economics of the time were that the $1200 of the machine was a lot more money relative to other costs (and paychecks) than today. If you don't believe me on the price, go look at advertisements from that time period (late 80s early 90s). I bought a machine that was "workstation" quality in/around 1994 for nearly $5000, which was a lot of money at the time (still is, but it was relatively more then). It wasn't the highest end CPU at the time even (only a Pentium-60, yes, with the bug, but the 90s were out) but it had 32M memory and the largest HDD available at the time (540M). Since 8M was the norm for the time, it'd be like getting a 4G machine today with a 300G HDD. What kind of machine can you put together for $5k today? What's the difference between having $5k in 1994 and having $5k today?

      Providing a unifying platform (both hardware and software) that was on the vast majority of PCs allowed hardware vendors to benefit from economies of scale just like software.

      Yes, PCs were starting to benefit from economies of scale (becoming commodity) during DOS (which... was MSDOS, btw, which was made by Microsoft as was Windows 3.1 and 95 and on) days but the full extent of commoditization hadn't been realized at the time. It took a unifying software architecture as well to complete the picture. So, Microsoft probably did help PCs to become commodities even, as DOS was Microsoft's thing.

    29. Re:Define "innovation" in that context. by _Sprocket_ · · Score: 1


      Take graphics cards, for example...

      What I think you're talking about here is really aimed at the 3D accelerator market. And that particular segment was rather young. Young markets do not often begin as commodity markets - it takes time. Even then, there were standards such as OpenGL that Microsoft initially supported. Of course, Microsoft then produced their own API and dumped OpenGL. The interesting piece here is that chipset developers are STILL working with OpenGL as well as Microsoft's API. So while working with Microsoft is certainly good business - I don't think it has quite the same effect as you're portraying it.


      "Commodity computing came about during the time of DOS - far, far before Windows." Simply stating this over and over without definition does not make it true. Did you ever buy a DOS machine? I did... several, and they were not really commodity. Sure, they were mass produced but they were not cheap (which is the other side of the 'commodity' coin). The prices of the machines back there were roughly what they cost now. You could get a decent machine for $1200 or so (today, I'd say you could get a decent machine for $600 though), however, the economics of the time were that the $1200 of the machine was a lot more money relative to other costs (and paychecks) than today.

      To begin with, commodity does not mean cheap... or even affordable. Driving down prices is an effect of commodity products in a free market. It is not the "other side of the 'commodity' coin". True - prices have dropped over the years. And a good part of the reason is commodity hardware. But there are also other factors such as economy of scale (more demand for microcomputers) and increased efficiencies gained by the new technology.

      Yes - I bought a DOS machine. A also bought a CP/M based Osborne 2 (Executive), a Commodore 64, and a couple TRS-80's (not to mention other machines from various bargain bin sales). There's a couple interesting things to note here. First - all the non-DOS systems were proprietary and cheaper than the DOS system. And the DOS system... well... it was a commodity box. It was a Compaq portable.

      Compaq blew open the commodity microcomputer market. They did it by turning the IBM PC in to a commodity platform.

      The IBM PC dominated the business computing market, arguably due to the IBM name. The IBM PC also made a strong showing in the home computer market since people were buying computers for home in step with what they were using at work.

      For the IBM PC to go from proprietary product to commodity platform, three distinct areas had to be tackled. First - the hardware. That was simple enough since the IBM PC was off-the-shelf components and IBM also published plenty of details about the inner workings of the IBM PC to attract peripheral manufacturers. The second part was the Operating System - again easy since this wasn't an IBM property (more on this later). The final part was the tough one - the BIOS. That was the proprietary gateway. Compaq spent a million dollars to reverse engineer the BIOS. They produced a better PC than IBM. And in doing so, they flung open the floodgates. It wasn't long before Tandy 1000 was getting kudos for the best bang-for-the-buck. And an entire industry of local computer stores piecing together systems on-order sprung up in strip malls around the world. It was also the beginnings of Dell... although they wouldn't become the dominating name years later.

      Let me stress something less it got lost in my rambling - the microcomputer industry was entirely proprietary up to the point that Compaq produced the first commodity systems. That is, systems built of specs that were not unique to Compaq. Others... many others... also producing compatible systems to these same specs solidified the commodity computing market. This was happening long before Windows became a household name.

      So what about DOS?

    30. Re:Define "innovation" in that context. by fitten · · Score: 1

      So in this respect, Microsoft does play an important role in the creation of commodity computing. But they did not create the market. And they certainly didn't create the market with Windows.

      I agree with this statement. I don't think they created it either, but I do think they helped it along a lot.

      And thanks for a good reply, it was a good read. It seems that you and I are "of an age". I, too, got my first computer before there was such a thing as an IBM PC.

    31. Re:Define "innovation" in that context. by _Sprocket_ · · Score: 1
      I agree with this statement. I don't think they created it either, but I do think they helped it along a lot.

      I completely agree. Microsoft played an important role; they were a key player. Having said that... I wonder what the current landscape would have been like if Digital Research hadn't waited so long to get CP/M ported to the 8086 or at least been willing to work with IBM earlier on.

      I, too, got my first computer before there was such a thing as an IBM PC.

      Yep. Odd world it is today compared to the early years when having a home computer was rare and a MODEM was completely bizzare.
  52. pseudo-academics should be careful what they bash by Anonymous Coward · · Score: 5, Insightful

    Have you actually read any of the papers?

    I am an OS academic, and we take Microsoft Research seriously, because they're fucking good.

    HotOS is a pretty serious workshop for Operating Systems research. Microsoft Research, among others, pays for the conference room. Singularity isn't far enough long yet to get into a bigger conference like SOSP or OSDI, but you can be sure it will in a year or two.

    I wouldn't call Singularity pseudo-academic.

  53. Remember the other definitions of Singularity by eyebits · · Score: 1

    Remember the other defintions of Singularity. They probably apply more than the one MS picked.

    - point where a mathematical function goes to infinity or is in certain other ways ill-behaved

    - so massive it implodes in on itself to become a black hole, etc

  54. that's different by jbeaupre · · Score: 2, Interesting

    Security means your safe. Dependability could mean that or that you can depend on being shafted on a regular basis. This is MS, so I'm guessing they mean the later.

    --
    The world is made by those who show up for the job.
  55. Eyecandy.... by VagaStorm · · Score: 1

    What! No screen shots?

  56. Let me guess... by kurbchekt · · Score: 0

    They're "borrowing" code from a free operating system? Let's say FreeBSD... Making a few changes and then resell it to the masses? Hmmmm... sounds familiar...

    1. Re:Let me guess... by jZnat · · Score: 1

      Nah, they're thinking of calling it OpenW32 and will be using a cute little daemon as its logo.

      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
  57. hahahahaha by xutopia · · Score: 1

    Service Unavailable

  58. Built on a new language? by PCM2 · · Score: 5, Insightful

    As far as I can see, the language in question is not exactly "new" anymore, being C#. In other words, this is sort of a demo OS written in a managed-code environment as a way to test various OS principles (which in this case sound a lot like the virtualization stuff that so many other vendors are also doing). Singularity seems like the equivalent of writing an operating system in Java for a school project.

    --
    Breakfast served all day!
    1. Re:Built on a new language? by Anonymous Coward · · Score: 0

      The language is Sing#, an extension to C#.

    2. Re:Built on a new language? by MyIS · · Score: 1

      Sort of like JavaOS? It's too bad that project didn't get much publicity...

      --
      http://zero-to-enterprise.blogspot.com/
    3. Re:Built on a new language? by Wesley+Felter · · Score: 1

      OTOH, JavaOS sucked so much that Sun would probably like to erase all evidence that it ever existed.

    4. Re:Built on a new language? by Coryoth · · Score: 4, Insightful

      As far as I can see, the language in question is not exactly "new" anymore, being C#.

      Actually its an extended version of Spec# which is in turn an extension of C#. It might help to acquaint yourself with what that actually means. The first significant different is that Spec# allows for explicit pre and post conditions and other formal specificiation syntax, and hence allows for model checking, extended static checking, and formal proof if required.

      It's more like someone writing an OS in BitC because it can be formally verified and hence be more secure. It does make sense, and there is good logic behind it. Comparing it to an OS in Java is just silly. Comparing it to an OS written in Java using JML and associated theorem provers is getting a little closer. Of course that doesn't address the issue of designing the OS to be more secure and reliable from the outset, and not just relying on formal verification.

      If you actually bothered to read some of the material on Singularity you would see that it is an ambitious, but remarkably interesting and promising project. It is also, I would expect, something that will permanently remain buried in MS research like so many other projects. I would be interested in seeing a good open source equivalent though - such a project might have some hope of surviving.

      Jedidiah.

    5. Re:Built on a new language? by LnxAddct · · Score: 1

      There is an operating system written in java. JNode.
      Regards,
      Steve

    6. Re:Built on a new language? by Anonymous Coward · · Score: 0

      Relying on a compiler for process protection that should be provided by hardware is an old idea and a bad one--unless you care more about writing papers than about real reliability.

    7. Re:Built on a new language? by GileadGreene · · Score: 1

      Relying on a hardware designer for process protection that should be provided by running on separate processors is an old idea and a bad one--unless you care more about convenience than real reliability.

    8. Re:Built on a new language? by Anonymous Coward · · Score: 0

      Relying on a flawed analogy to substitute for a valid argument is an old idea and a bad one--unless you care more about appearing clever than intellectual honesty.

    9. Re:Built on a new language? by GileadGreene · · Score: 1
      Relying on pithy one-line assertions rather than reasoned argument based on actual facts is an old idea and a bad one--unless you care more about winning an argument than contributing to a useful discussion.

      Not to mention the fact that using ad hominem attacks ("...unless you care more about writing papers than about real reliability...", and "...unless you care more about appearing clever than intellectual honesty...") as part of your assertions is among the worst kinds of logical fallacy.

    10. Re:Built on a new language? by Clith · · Score: 1

      Sounds like they've re-invented Eiffel. :-/

      --
      [ReidNews]
    11. Re:Built on a new language? by Coryoth · · Score: 1

      It's probably closser to SPARK, but yes, it's the same general idea though in this case with the little more emphasis on static analysis and theorem proving. Eiffel is great though - I wish more people would use it, or something similar like SPARK, JML, Spec# etc.

      Jedidiah.

    12. Re:Built on a new language? by Anonymous Coward · · Score: 0

      My original comment was, admittedly, a little snarky. This is Slashdot, after all. I'm not much interested in winning an argument or in contributing further to a discussion that I believe would probably not be particularly useful. I could spend a lot of time formulating closely-reasoned arguments for my point of view, but no one would change their research agenda. I don't have time to participate in yet another pointless intellectual dick-size war on Slashdot that'll slip silently below the waves in less than a day.

      The intent of my original comment was to point out that there is another point of view on this issue. To wit, that the idea under discussion is (1) old (it was current when I was in graduate school 20 years ago) and (2) worthless if your goal is reliability. The latter assertion is not as easy to prove, but the intuition is that relying on lots of incredibly complex software to guarantee the reliability of other software (rather than on hardware that is a few orders of magnitude less complex) is building your house on sand. I'll leave it at that. A word, to the wise, is sufficient. (But note that this comment is in reply to you, GG, hence the excessive length.)

      Part of the motivation for my original comment (and the snarky tone) was that the computing field is full of snake oil, and I'm sick of it.

      The intent of my second comment was to punish you for your pitiful attempt at a smart-ass rejoinder. Mission accomplished, I think.

    13. Re:Built on a new language? by fnc · · Score: 1

      As said in another post, it not C#. It is a extension of C# called Sing# (saying that it is C#, is like saying C++ is the same as C). The differences are pre, pos-conditions and invariants, and a new model of concurrency similar to CSP (message passing).

    14. Re:Built on a new language? by GileadGreene · · Score: 1
      I'm not much interested in winning an argument or in contributing further to a discussion that I believe would probably not be particularly useful.

      Then why post in the first place?

      The intent of my original comment was to point out that there is another point of view on this issue.

      Which is certainly an admirable intention. It's the execution that I take issue with.

      To wit, that the idea under discussion is (1) old (it was current when I was in graduate school 20 years ago)

      As is much in the world of computer science. Sadly, a lot of it hasn't actually been applied in the mainstream - there's a reason the Lisp zealots keep complaining that everybody is only just now starting to implement ideas from Lisp. I imagine it'll be another decade or two until we see any of Milner's or Hoare's work on concurrency really hit the mainstream.

      and (2) worthless if your goal is reliability. The latter assertion is not as easy to prove, but the intuition is that relying on lots of incredibly complex software to guarantee the reliability of other software (rather than on hardware that is a few orders of magnitude less complex) is building your house on sand.

      And yet your intuition may be wrong. Your argument depends critically on the complexity of the software charged with maintaining process isolation, and I doubt either you or I have any idea of how complex the Singularity system actually is. Meanwhile, things like Ericsson's Erlang system provide proof that software-only systems can be used to provide robust process isolation for industrially critical systems.

      A word, to the wise, is sufficient. (But note that this comment is in reply to you, GG, hence the excessive length.)

      Har har har. My, what a stinging wit you have.

      Part of the motivation for my original comment (and the snarky tone) was that the computing field is full of snake oil, and I'm sick of it.

      Aren't we all. But I'm also sick of naysayers who make blanket assertions with little or no evidence to back them up. Neither really contributes anything useful to solving the larger problem of building useful systems that work as they are intended to.

      The intent of my second comment was to punish you for your pitiful attempt at a smart-ass rejoinder. Mission accomplished, I think.

      Think again. No, really, give it a try. Why on earth would you want to "punish" in the first place (especially given your original - self-admitted - snarky tone)? Why not take my original comment as a challenge to explain your position further (as you have finally done now)?

    15. Re:Built on a new language? by Anonymous Coward · · Score: 0

      I'm both lazy and pressed for time, so I'll adopt your method of reply.

      Then why post in the first place?

      My very next comment answers your question. Were you replying on the fly?

      Which is certainly an admirable intention. It's the execution that I take issue with.

      I thought the execution was rather elegant.

      As is much in the world of computer science. Sadly, a lot of it hasn't actually been applied in the mainstream - there's a reason the Lisp zealots keep complaining that everybody is only just now starting to implement ideas from Lisp.

      This is the first intelligent thing you've said. However, there are different types of old technology. Some, like Lisp, have great value but the unwashed masses are unable to see it. Others, like speech recognition, are utterly fraudulent and required thirty years to show even very marginal utility. Guess which I consider to be most similar to Singularity?

      And yet your intuition may be wrong.

      My God, of course it may be wrong. It's an intuition. I happen to think it's correct, though.

      Your argument depends critically on the complexity of the software charged with maintaining process isolation, and I doubt either you or I have any idea of how complex the Singularity system actually is.

      Holy horseshit, Batman, is this the best you can do? Argument from ignorance? I thought you must have some stake in all this, given your tenacity. So what are you doing, just trying to be the morality police on Slashdot?

      Meanwhile, things like Ericsson's Erlang system provide proof that software-only systems can be used to provide robust process isolation for industrially critical systems.

      I wouldn't say Erlang's not cool, but I'm assuming that Singularity is aimed at general-purpose mass-market computing, where the system is much more subject to malicious hackers and idiot programmers than the kinds of industrial systems Erlang is used for. You're asking me for real arguments, but you can't seem to come up with any that aren't fatally flawed.

      Har har har. My, what a stinging wit you have.

      Thanks. Sometimes I think it's the only thing that keeps me sane. (There's your opening--go for it!)

      Aren't we all. But I'm also sick of naysayers who make blanket assertions with little or no evidence to back them up. Neither really contributes anything useful to solving the larger problem of building useful systems that work as they are intended to.

      Maybe if more people had listened to the nay-sayers, we wouldn't have had to endure the tech crash of the last five years. This field needs more nay-sayers, not fewer.

      And, again, Slashdot isn't really the place to make useful contributions. If I wanted to contribute in this area, I'd be publishing papers. (Or better yet, building systems, but I'm not a hardware guy and the consensus these days seems to be that computer architecture--at the semantic level, not silly performance games--should never progress much beyond the Intel 80386.)

      Think again. No, really, give it a try.

      This is funny, coming from you.

      Why on earth would you want to "punish" in the first place (especially given your original - self-admitted - snarky tone)?

      I'm a sadist. If you were a girl, I'd spank you.

      Why not take my original comment as a challenge to explain your position further (as you have finally done now)?

      Because it results in tedious long-winded exchanges like this.

      But, seriously, don't let me discourage you. You're obviously young. Don't lose your enthusiasm for the field (that is, unless you should decide you want to make any money). Maybe one day you'll get a clue.

      You may have the last word. I'll probably even read it, but I doubt I'll respond again. Farewell.

    16. Re:Built on a new language? by GileadGreene · · Score: 1
      Holy horseshit, Batman, is this the best you can do? Argument from ignorance?

      Huh? I'm not arguing anything at all. I'm just pointing out that your assertions are meaningless if you are ignorant of how the Singularity system is constructed.

      I wouldn't say Erlang's not cool, but I'm assuming that Singularity is aimed at general-purpose mass-market computing, where the system is much more subject to malicious hackers and idiot programmers than the kinds of industrial systems Erlang is used for.

      Nevertheless, it demonstrates that software-based process isolation can work robustly in systems where correct functioning is critical. Is it necessarily the ideal system for a mass-market product? No. That's why research projects like Singularity are useful.

      This field needs more nay-sayers, not fewer.

      No doubt. Though it'd be nice if they could bring reasoned argument to the table, rather than prejudice. Otherwise I'll be taking them with the same large grain of salt that I take the marketing bozos.

      This is funny, coming from you.You know, your constant use of ad hominem, coupled with the generally condescending tone of your posts, really does very little to reinforce your arguments. It just makes you appear insecure.

      You're obviously young.

      Oh, obviously. Just as obviously, IHBT. Oh well, HAND.

  59. Executing in ring 0 by Husgaard · · Score: 1
    Not much to say about this OS until Microsoft learns how to keep their server alive during a slashdotting...

    But from the second link it seems that almost everything - including user programs - executes in socalled Software Isolated Processes (SIPs), and that these SIPs all run in ring 0.

    [sarcasm] Looks to me like Microsoft is working hard to keep their current security leadership... [/sarcasm]

  60. good for niche marked by spectrokid · · Score: 2, Insightful

    An OS written in C#? Could be good. Not for a gaming machine, but what about an ATM? A controller in an industrial environment? Imagine a PC with no memory leaks,like ever. No buffer overflows. No monthly patching hell. Would make one tough SOB as a firewall.

    --

    10 ?"Hello World" life was simple then

    1. Re:good for niche marked by Alioth · · Score: 1

      Ah, so basically Microsoft has got tired of copying Apple and have decided to copy OpenBSD instead!!

      OK, OK, mod me down now.

  61. Microsoft Singularity by Anonymous Coward · · Score: 0

    The deeper you get into it, the slower your work goes.

  62. singularity? sounds like the borg.. by know1 · · Score: 0

    "I am singularity of microsoft"
    "you will be assmutilated"

  63. Let me guess... by AutumnLeaf · · Score: 1


    It's named "WinUX."

  64. Yeah... by dep01 · · Score: 1

    In stark contrast to Windows XP's vision of "performance over dependability."

    --
    "hey, could you pass me a paper towel? er.. I mean... DEPLOY ABSORBTION PANEL!"
  65. Not really by I+Like+Pudding · · Score: 3, Funny

    Black holes can't destroy information nearly as well as an MS OS can.

    1. Re:Not really by Anonymous Coward · · Score: 0

      Data isn't information. The term information implies interpretation and usefulness. So... if your data becomes inaccessible, and therefore unusable, when it is sucked into the singularity, then it isn't even data anymore, let alone information. Perhaps Microsoft will hire Devo for the new ad campaign!

    2. Re:Not really by I+Like+Pudding · · Score: 1

      You picky motherfucker.

  66. That isn't the question. by khasim · · Score: 0, Troll

    The question isn't whether they've made flawed products.

    The question isn't whether they make flawed products.

    The question is what have they made that's "innovative".

    If they haven't made anything "innovative", then by definition, their products are copies and derivatives of others.

    Don't get upset over the word. I'm sure that you'd buy a new car even if there wasn't a single bit of it that was "innovative".

    And "innovative" does not mean "better" or "best" or "great" or anything other than "innovative".

    1. Re:That isn't the question. by toleraen · · Score: 1

      The question is what have they made that's "innovative".

      Would their Virtual Wifi count as "innovative" to you? Their site seems to be /.'d a little, but that's one thing that comes to mind. Like the GP suggested, browse through their site some time.

    2. Re:That isn't the question. by Eric604 · · Score: 1

      I think the "start -> shut down..." GUI design is pretty innovative.

    3. Re:That isn't the question. by linuxfanatic1024 · · Score: 1

      I think the "start -> shut down..." GUI design is pretty innovative.

      Isn't that illogical? Clicking Start to shut down the computer? I always thought that was the dumbest part of M$ Windows when used it in the past.

      --
      Microsoft-free since March 28, 2004
    4. Re:That isn't the question. by Pantero+Blanco · · Score: 1

      Someone just failed a humor check. I had plenty of problems with Windows when I used it at home, and still do when I wind up using it on the job, at a library, et cetera, but the name of the Start button wasn't one of them. "Menu" might've made more sense, but...Meh.

  67. But wait! by avp0 · · Score: 0

    April 1st is 6 mos. away.

    --
    PETA - People Eating Tasty Animals!
  68. Great new 'word' by Skiron · · Score: 1

    'Singularity'; Usually associated with blackholes->money.

    Will business never learn if anyone takes this up as another 'innovation' for the supposedly next best thing to sliced bread rather than MS's usual maloney?

  69. In another world.. by Anonymous Coward · · Score: 0

    If this was a Google project, everyone would be praising it.

    1. Re:In another world.. by Widowwolf · · Score: 1

      Well everything that google has put out hasn't been comlete failures like almost all off Microshafts. #2 at least google gives it back to open source, #3 and most important so listen up...Bill Gates does own google..Once Microshaft comes out with a decent OS that is secure, reliable and doesnt cost and arm and a leg, then maybe the bashing will stop. We are sick of the lies spewed by Microshaft. Plain and simple

      --
      ~~"Of course, that's just my opinion. I could be wrong." ~~Dennis Miller
  70. Wow, what a concept! by neural+cooker · · Score: 1
    Quote from one of their papers:

    "Singularity is a research project in Microsoft Research that started with the question: what would a software platform look like if it was designed from scratch with the primary goal of dependability?"

    Um, is it just me or isn't this the primary goal of just about every operating system built since practically the first OS (but, obviously excluding OS's from MS). They could just pick up a 25+ year old book on operating system concepts to know how to build this thing. This is not a new concept by any stretch of the imagination. But I guess if MS didn't "invent" it then it can't be taken seriously by MS.

    1. Re:Wow, what a concept! by Master+of+Transhuman · · Score: 1


      I agree. It would have been better had they started from the premise that an OS should be CORRECT in achieving the goals of being reliable, fast and secure (plus the principles stated below.)

      Typical Microsoft Geek Moron(TM) lack of comprehension of the function of anything. What you get when you hire twenty-four year olds out of college after passing a puzzle test.

      The proper principles for software are what I call the "3C's": Comprehension, Cooperation, Communication. Software should be comprehensible, work well with others, and be clear in its operation. More importantly, on a deeper level, software should have some form of understanding of what it's doing (so it can tell you when something goes wrong - or fix itself), should interoperate well with other software and users, and communicate clearly to same.

      Nothing on the market comes close to having these qualities.

      --
      Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
    2. Re:Wow, what a concept! by cerelib · · Score: 1

      Yes, because we all know that Linux is immune to buffer attacks. This is actually an innovative idea that I would like to see implemented.

    3. Re:Wow, what a concept! by k-zed · · Score: 1
      The proper principles for software are what I call the "3C's": Comprehension, Cooperation, Communication. Software should be comprehensible, work well with others, and be clear in its operation. More importantly, on a deeper level, software should have some form of understanding of what it's doing (so it can tell you when something goes wrong - or fix itself), should interoperate well with other software and users, and communicate clearly to same.

      That really sounds like the old unix principle to me. Like all those (base|file|text)utils..
      --
      we discovered a new way to think.
    4. Re:Wow, what a concept! by Locke2005 · · Score: 1

      Uh, no. I'm not an OS expert, but I beleive NT 3.1 kept drivers in a seperate protection ring from the kernel (much like OS/2) so that 3rd party drivers couldn't crash the kernel. Since this was incredibly slow due to constant context switches between drivers and kernels, for NT 3.5 Microsoft made the concious desision to make the OS less reliable by putting the drivers in the same protection ring as the kernel to improve speed. As far as I know, subsequent MS OSes have kept this same trade-off, allowing drivers to corrupt the system in order to improve performance. I beleive Linux drivers can pretty much futz up the kernel too.. at least from personal experience with the driver I'm currently writing, accessing a NULL pointer from within a driver causes an exception and a reboot. Presumably Linux also sacrifices memory space protection to gain speed.

      --
      I've abandoned my search for truth; now I'm just looking for some useful delusions.
    5. Re:Wow, what a concept! by Anonymous Coward · · Score: 1, Insightful

      Coming from a guy who's never written a piece of sizable software himself.

      You really are a fool. You know that right? It would be a damn shame if you went through life without finding out you really aren't as smart or important as you think you are.

    6. Re:Wow, what a concept! by drsmithy · · Score: 1
      Uh, no. I'm not an OS expert, but I beleive NT 3.1 kept drivers in a seperate protection ring from the kernel (much like OS/2) so that 3rd party drivers couldn't crash the kernel. Since this was incredibly slow due to constant context switches between drivers and kernels, for NT 3.5 Microsoft made the concious desision to make the OS less reliable by putting the drivers in the same protection ring as the kernel to improve speed. As far as I know, subsequent MS OSes have kept this same trade-off, allowing drivers to corrupt the system in order to improve performance.

      * OS/2 didn't do this.

      * The switchover with NT's driver model you are talking about happened with NT4 (so 3.1, 3.5 and 3.51 were the more microkernel-ish implementation). The primary reason behind it was display driver performance.

      * Microsoft have been trying to get back to a more microkernel-ish design over the years (as hardware performance has improved so dramatically), although most stuff still runs in ring 0.

  71. Non-mainstream? by AndreiK · · Score: 1

    This OS seems like it is much more suited for server applications - where if one process fails, it doesnt crash the system.

    Gee, that sounds familiar?

  72. They aren't the first by ndogg · · Score: 5, Informative

    Check out EROS for an implementation that exists now. Granted, EROS itself is no longer being developed, it was definitely around before this OS, and EROS has spawned some new projects (look on the link for links).

    --
    // file: mice.h
    #include "frickin_lasers.h"
    1. Re:They aren't the first by justins · · Score: 1
      Check out EROS [eros-os.org] for an implementation that exists now. Granted, EROS itself is no longer being developed, it was definitely around before this OS, and EROS has spawned some new projects (look on the link for links).

      OMFG MS Sux they're ripping them off OMFG they've never done anything original OMG LOL!!!!!!11111111
      --
      Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
  73. You guys are fucking retards... by Anonymous Coward · · Score: 0

    The title says it all.

  74. The problem with Singularity is it isn't Windows by Anonymous Coward · · Score: 0

    The reason most of us run Windows isn't the security or the fine architecture, it's the apps. I think my Windows 2003 is quite reliable, but I realize that a lot of what runs under the hood is not pretty. This Singularity sounds nice in concept, but until it runs my apps, I'm not biting. The slow MS move to apps written in .Net proves that it is not a trivial matter to rewrite all those productivity apps in managed environments and I've yet to see a game in a managed app. A lot of the same architectural mistakes can be repeated even in a managed space as they rewrite more of the lowlevel API and OS stuff in .NET. I have no doubt the concept of a Singularity type OS sounds great, but without the apps, it stays a lab experiment for now. We will see DNF before we see Singularity.

  75. Delliver, dont just talk. by miffo.swe · · Score: 1

    When it comes to Microsoft its hard to take them seriously. Considering how much of Windows Vista and its predecessors that came out as real products and functionality everything is just pointless PR blabber. Until we see something that runs on a computer its all about appearence. Heck RMS can issue a press release tomorrow claiming to have invented an unbreakable system that can run on a calculator. Microsoft has done this before and continually does it to stop people from migrating through vaporware. "-The next version will be secure" "This new version is going to be faster than the older ones" etc...

    --
    HTTP/1.1 400
    1. Re:Delliver, dont just talk. by Noehre · · Score: 1

      Someone obviously doesn't understand that its a research project.

    2. Re:Delliver, dont just talk. by miffo.swe · · Score: 1

      im perfectly aware of that but i am just as aware of the fact that we havent to date seen anything from any Microsoft research project materialising as any products. Their entire research seems more like a PR act than anything else.

      --
      HTTP/1.1 400
  76. Amazing by Rodness · · Score: 1

    Microsoft is well known for spouting "Everything before now was crap. We did it right this time." as a marketing ploy to sell new versions of their OS.

    However, I'm surprised that they're pulling that out before Vista's even on the shelves. Of course, maybe they're just hedging their bets because Vista is probably vaporware...

  77. uh oh by hitchhacker · · Score: 1


    let's all hope it doesn't have anything to do with technological singularity!

    coming soon.. MS Skynet

    -metric

    1. Re:uh oh by Master+of+Transhuman · · Score: 1


      We wish.

      Not from Microsoft. No way, Jose.

      More likely, they've invented Ah-nuld. Something to beat more customers into submission and take their money.

      They should rename all their OS "Bank Account Drainer."

      --
      Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  78. IIS doesn't benefit from this design philosophy by Anonymous Coward · · Score: 0

    Server Error in '/' Application.

    Runtime Error
    Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

  79. wish list - clean upgrades by wkk2 · · Score: 1

    I don't believe that we will really have dependability until upgrades can be installed without rebooting or restarting the OS or applications.

  80. It's agood thing and they Should be persuing it. by romanbway · · Score: 2, Insightful

    As software starts to take over from mechanical controls it needs to be super reliable. It looks like Microsoft is getting ready for a world where their software flies our planes and drives out cars.

  81. "Boarder application" ? by Anonymous Coward · · Score: 0

    What does "Boarder application of static verification" mean?
    Is that anything like "Broader application of static verification"?

    From www.dictionary.com:
    boarder1 Audio pronunciation of "boarder" ( P ) Pronunciation Key (bôrdr, br-)
    n.

            One who boards, especially:

                  1. One who pays a stipulated sum in return for regular meals or for meals and lodging.
                  2. One who goes on board a vessel as part of an assault or military action: repel all boarders.

    I think Microsoft Research should work on creating a grammar checker before trying to develop a decent operating system.

    1. Re:"Boarder application" ? by Master+of+Transhuman · · Score: 1

      1. One who pays a stipulated sum in return for regular meals or for meals and lodging - or software (see "Subscription Pricing.")

      2. One who goes on board a vessel as part of an assault or military action: repel all boarders. (See "Linux as Threat to Microsoft.")

      Sounds like Microsoft's thinking to me.

      --
      Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  82. submit this - i'm lazy by Anonymous Coward · · Score: 0

    guy loses a finger to gangsters wanting his car... http://news.bbc.co.uk/2/hi/asia-pacific/4396831.st m

  83. Just like studying history... by Kevin+Burtch · · Score: 1


    "Those who fail to learn from Unix are doomed to repeat it" - unknown

    Welcome to 1969 MicroSoft! :)

    --
    - Preferences: Solaris 10 (servers), Ubuntu (desktops), Solaris 11 (personal servers) -
  84. Which one wears the Tony? by FishandChips · · Score: 1

    I thought Vista was meant to be a whole new operating built from the ground up with dependability - not to mention security - in mind? Oh well. I guess I'll just have to pretend that's what Vista is all about while waiting 20 years for Singularity. Actually sounds an extremely interesting idea but perhaps it won't see the light of day till Gates and co have gone.

    Hmmn, a completely new operating system from Microsoft: "It's a complete lie, of course. But you can't afford to be too scrupulous when you have world domination in mind." E.L. Wisty

    --
    Las qué passoun
    tournoun pas maï
  85. Re:pseudo-academics should be careful what they ba by networkBoy · · Score: 0, Troll

    I won't trust the security of a M$ OS until the source is opened. (Note I don't mean open source, just that the source is available to all for peer review, even if full copy and distrobution rights are maintained).
    -nB

    --
    whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
  86. MS has written an OS from Scratch! by arfonrg · · Score: 1

    I believe that TRSDOS (or at least it's predecessor) was written by BillyG and crew from scratch.

    --
    Your thin skin doesn't make me a troll
    1. Re:MS has written an OS from Scratch! by filesiteguy · · Score: 1

      Yes. Bill and buddies wrote several compilers. AFAIK there were: Altair, TRS-80, Apple BASIC, Q-BASIC and possibly others.

  87. Obligatory John Titor comment. by acslat3r · · Score: 1

    Well I guess John Titor was a bit off when he predicted we would harness the power of a singularity. Instead of time travel we get a crappy pre-pre alpha research OS..while he came back bending lasers and building time machine devices resembling a toolbox. I guess this is how our universe differed from his.

  88. Singularity Now. Insanity Later. by wernst · · Score: 1
    There are so many jokes that come with this name that its not even funny.

    The situation, that is.

    Not the jokes.

    Well, maybe the jokes too...

  89. CmdrTaco by Anonymous Coward · · Score: 0

    Takes it up the ass from Whorevalds himself. Get your mouth of his miniscule cock, Taco. You're just another faggot Linsux zealot =]

    1. Re:CmdrTaco by Master+of+Transhuman · · Score: 1


      Bill, Steve says answer your email: another of our servers has crashed from those damn Linux zealots at Slashdot.

      --
      Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
    2. Re:CmdrTaco by Anonymous Coward · · Score: 0

      mod please? although if i werent worried about this site being appropriate, i'd say leave it up as an example of ignorance

  90. You didn't actually read any of their whitepapers by stlhawkeye · · Score: 1
    So here you.

    Singularity is a research project in Microsoft Research that started with the question: what would a software platform look like if it was designed from scratch with the primary goal of dependability? Singularity is working to answer this question by building on advances in programming languages and tools to develop a new system architecture and operating system (named Singularity), with the aim of producing a more robust and dependable software platform. Singularity demonstrates the practicality of new technologies and architectural decisions, which should lead to the construction of more robust and dependable systems.

    Where have I hear that before?.

    A key aspect of singularity is ... Software-Isolated Processes, which encapsulate pieces of an application ... and provide information hiding, failure isolation, and strong interfaces. All code outside the kernel executes in a SIP.

    That sounds alarmingly like a closed address space. Microsoft in 2005 is giving us what UNIX had over 30 years ago. thx u sir!

    SIPs are closed object spaces, not address spaces

    I stand corrected! What's the difference?

    Two Singularity processes cannot simultaneously access an object.

    Ruh ruh! So we're going back to the model where two processes can't open a handle to the same file? You mean ... like .. er... DOS?

    A process cannot dynamically open or generate code.

    So like ... you can't run Perl on it. Or shared libraries. #include <dlfnc.h> is a thing of the past.

    SIPs are created and terminated by the operating system, so that ... resources can be reclaimed.

    Yeah uhhh... the runlib library for, say, C executables in UNIX does this. And has for a long time. Like, since Gerald Ford or something.

    I'd go on but I'm just making fun of them. If you read through their overview document there's actually some very good ideas in there, and knowing a few programmers from W2K, I can tell you that they do employ some top-notch talent there.

    --
    "I have never won a debate with an ignorant person." -Ali ibn Abi Talib
  91. Microsoft: ActiveX considered harmful by cbiffle · · Score: 2, Insightful
    My favorite bit from the research paper (linked from TFA) is the following:


    Extensions are a major cause of software reliability, security, and backward compatibility problems. Although extension code is often untrusted, unverified, faulty, or even malicious, it is loaded directly into a program's address space with no hard interface, boundary, or distinction between host and extension.


    Okay, Microsoft, I think I'm with you on this one...you're telling us not to use ActiveX, right?
    1. Re:Microsoft: ActiveX considered harmful by Master+of+Transhuman · · Score: 2, Interesting


      No, they're saying that the OS should only run software from the original developers and never be enhanced by anyone else - ESPECIALLY anything that could remotely be considered "open source."

      In other words, users must only run Microsoft Windows - and stop asking us for updates and security patches because updates and patches are not reliable or secure.

      In other words, give us your money and shut the fuck up.

      Oh, yeah, this project has Bill's seal of approval on it, all right.

      These are the sort of "brilliant guys" Microsoft hires - people with no fucking clue who accept the Microsoft way of doing things.

      The concepts mentioned, by the way, are 180 degrees opposite of mine: an application should just be one more thing the OS knows how to do. In other words, total integration of OS and applications by requiring the application to be developed in the same manner as the OS as - not an extension - but an integration with the OS.

      Not possible without an OS with conceptual processing ability, however.

      --
      Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  92. If Star Trek has taught me anything.. by mandreko · · Score: 1

    Stay away from the singularities!

  93. Sing# ???? by Anonymous Coward · · Score: 0

    from TFA: "Singularity is written in Sing#, which is an extension to the Spec# language developed in Microsoft Research. Spec# itself is an extension to Microsoft's C# language" Let the punishment continue....

  94. Old ideas by Anonymous Coward · · Score: 0

    These ideas are really old. I saw the exact same concepts in grad school about 10 years ago. An additional part from school that I didn't see on the Singularity page is that an operating system like this would enable hardware to be simpler and faster. In other words, CPUs would not need all the memory protection and access priveledge control built in, it would be enforced by the software. It is an interesting concept but the security and stability of your system would depend on how good your compiler/language/runtime are. Find a security hole in any one of these and your whole system is hosed.

  95. Dependability!? I'd read, but the server's dead :) by toby · · Score: 1

    n/t

    --
    you had me at #!
  96. bogus by samantha · · Score: 1

    Why on earth would I not allow a SIP to modify its own code? Certain types of advanced computation are not easily done without it. If it is so bloody self-contained why should anyone care? Curtailing languages and programming to only what can be statically verified even within ultimate sandboxes is pointlessly restrictive for highly illusory "safety". Say goodbye to Python, Ruby, Perl, Lisp, Scheme and all those other "unsafe" languages. It also allows M$ unprecedented ability to control all code run, which I imagine has not escaped them.

    This is a giant Microsoft FUD attempting to ride on the recent Singularity press. Microsoft has no real place in a real technological Singularity. Don't drink the koolaid served by the Redmond Dinosaur.

  97. ln -s Singularity Java\ Desktop by Anonymous Coward · · Score: 0

    Right?

    1. Re:ln -s Singularity Java\ Desktop by Anonymous Coward · · Score: 0
      More like
      ln -s /dev/null Singularity
  98. What? by HunterZ · · Score: 1

    "...designed with emphasis on dependability instead of performance."

    I thought that was the point of Windows NT? So I guess there'll be 3 versions of Singularity and then they'll make a home version (a la XP), and then they'll start over from scratch again?

    --
    Arguing about vi versus Emacs is like arguing whether it's better to make fire by rubbing sticks or banging rocks.
  99. Me too by Anonymous Coward · · Score: 1, Informative

    I've hacked on this project also. It's a microkernel architecture akin to Mach. But they have some pretty interesting ideas on performance and the programming model (they have their own C# language extension). Like the parent said, this is a research prototype and nothing like Windows. Also, don't let the absence of a sosp/osdi paper bother you too much. There is surprising little whole systems os research done in academia anymore. It just takes too many people and too much time to do well; MSR is one of the few places with enough resources to be able work on a system like this.

  100. Where is the innovation? by Anonymous Coward · · Score: 0
    Advances in languages, compilers, and tools open the possibility of significantly improving software.
    Turing proved that in general all languages are essentially the same. All you can do is tweak with the abstraction in the vertical (i.e. low vs. high level) or the horiztonal (bredth of intrinsic functionality). Can Microsoft really innovate much here? If one considers that C# is their latest and greatest language "innovation" then all we can hope for is that they reinvent the wheel still one more time.
    For example, Singularity uses type-safe languages
    Oh boy! Now there is real innovation for you. How many decades have we had type-safe languages now? This also carries with it the implied over-head of a type-safe language. Still, I am sure the hardware manufacturers will be more than delighted to sell everyone faster and faster bloatware-friendly CPUs.
    an abstract instruction set to enable what we call Software Isolated Processes
    Ummmm, where have I heard of something similar to this before. Let me think. Ummmm, ummm...OH YEA! The Java run-time environment. Or any environment running an abstract instruction set. Anyone here old enough to remember P-Code interpreters?
    SIPs provide the strong isolation guarantees of OS processes
    yea, yea, yea, just like Java processes execute in their own virtual space...blaugh, blaugh, blaugh. So I haven't heard about anything innovative yet.
  101. I hope they market this SOB by WhiteWolf666 · · Score: 3, Insightful

    Thoughts:

    1. Be nice to have some real competition versus Linux/OS X in terms of architecture. XP/2003 just aren't there. Vista won't be, most likely.
    2. Where such a beast (research OS) ever to become a product, would it demonstrate a high level of backwards compatibility? If not, would it actually have to compete on merits, rather than vendor lock-in?
    3. It's taken ~10 years to write Wine to the point where it is in _beta_. Now, I'm sure MS can do it faster, because they have the documentation; after all, they designed it. But how long will it take? Or will they use a virtual machine architecture?

    In any case, if MS switches to an entirely different OS architecture, I forsee the end of the MS monopoly. Release of a non-Win32 based OS, one that runs older applications (either desktop OR server) in emulation validates Linux/OS with QEMU/Virtual PC/VMware/Xen/Whatever.

    4. I doubt this will ever leave the lab. Singularity will be a test bed for MS researchers who want to play with various concepts. These things will be ported over to Vista, or whatever comes into the future. I cannot imagine a world in which MS actually started from scratch; having to market such a product against mainline-Windows, Mac OS X, Linux, Solaris, AIX, and FreeBSD would be pure madness. It's already extremely difficult for MS to push Office against older versions of Office; this has generated substantial pressure towards alternative Office packages.

    It'll be significantly harder for MS to push towards a non-Windows MS operating system. Every single CIO willing to consider moving from Windows will be willing to consider moving to Linux/OS X/whatever instead.

    --
    WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
    1. Re:I hope they market this SOB by Wesley+Felter · · Score: 1

      Be nice to have some real competition versus Linux/OS X in terms of architecture.

      It would, but I don't think the desktop/server market can support any new OSes. Cell phones and game consoles are another matter.

      Were such a beast (research OS) ever to become a product, would it demonstrate a high level of backwards compatibility?

      Singularity is totally incompatible with everything else. I suspect MS would use the Windows Hypervisor to run both Singularity and Windows at the same time if they want compatibility.

      I doubt this will ever leave the lab. Singularity will be a test bed for MS researchers who want to play with various concepts.

      Absolutely. That's the point of research.

    2. Re:I hope they market this SOB by Master+of+Transhuman · · Score: 0, Flamebait


      Nah - they'll just run a Virtual Machine on top of Singularity - and run Windows Server VX (Very Expensive) 2008 on top of it.

      Which means your system will crash regularly and be slow as molasses - but this situation will be very dependable.

      The CIOs will eat it up! After all, they won't have to re-train any employees or buy any new software (well, after upgrading the OS, of course, on a five-year locked-in subcription plan at a fifty-percent increase in rates due to the "dependability" feature, and buying the new Microsoft Office VX (Viciously Expensive) version released at the same time.)

      This is a guaranteed winner for Bill!

      --
      Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
    3. Re:I hope they market this SOB by courtarro · · Score: 2, Insightful
      Wow, quick to judge. Once MS has given up the push for performance (as in this case), you can guess they're not aiming at the end-user desktop. They don't want this to compete with Vista or any future derivative, they will want it to be used in embedded systems that can't fail. They want it to compete with Linux for small devices, not on the desktop. In cars, IV drips, air traffic controllers, and voting machines, you need computers that never ever crash, so this is the sort of thing that can be used in those lower-performance-allowable situations.

      That said, this is research. They have barely even made it known to the public at this point, much less secured some sort of massive marketing campaign. They may later decide that it's pointless to compete with existing solutions (I couldn't say either way), but the only way to find out is to start something and see where it goes.

    4. Re:I hope they market this SOB by TekGoNos · · Score: 1
      Where such a beast (research OS) ever to become a product, would it demonstrate a high level of backwards compatibility?

      Well, of course not!
      The whole idea of this OS is to replace this OS permission checks by language restrictions. Basicly, they use a language (C# or Java) that encapsulate all memory addresses in references. So : no pointer arithmetics, no manipulation of the system pointer, no using other SIP's data (as we have no reference to it), etc ...
      The idea is very interesting. Many security bugs come from allowing direct access to the processor and memory. Languages with a VM encapsulate this, but the OS still pays the price in complexity to prevent exploits in "native" code.

      Now, this also means that ONLY code written in managed languages will run on this system, and backward compatibility is therefor toast. No C allowed, no assembler, etc ...

      This also makes it hard to port ideas to mainstream windows, as mainstream windows (and every other major OS) still needs to protect its ressources from direct access.

      --
      I have discovered a truly remarkable proof for my post which this sig is too small to contain.
    5. Re:I hope they market this SOB by Bonobo_Unknown · · Score: 2, Insightful

      Microsoft didn't seem to have too much trouble in getting everyone to swap from 9x to NT (What version of NT are we up to now, is it 6??)

      --
      We don't believe in radical loony monotheistic religions from the middle east -- we're Christians.
    6. Re:I hope they market this SOB by Clover_Kicker · · Score: 1

      Heh, there's still a whole lot of 9x out there being used every day.

    7. Re:I hope they market this SOB by drsmithy · · Score: 2, Insightful
      Be nice to have some real competition versus Linux/OS X in terms of architecture. XP/2003 just aren't there. Vista won't be, most likely.

      Architecturally, NT is better than both Linux and OS X.

      Release of a non-Win32 based OS, one that runs older applications (either desktop OR server) in emulation validates Linux/OS with QEMU/Virtual PC/VMware/Xen/Whatever.

      Except that Microsoft would expend a great deal of effort to make the emulation transparent, seamless and easy to use. It's doubtful the same would be true from the OSS community.

      It'll be significantly harder for MS to push towards a non-Windows MS operating system.

      Not if it runs existing applications relatively seamlessly, it won't.

      Every single CIO willing to consider moving from Windows will be willing to consider moving to Linux/OS X/whatever instead.

      Assuming they can provide similar functionality and performance at a competitive price. This is far from a given.

  102. I wonder... by Howler · · Score: 1

    What distro are they going to base it on?

  103. Skip the web page and grab the PDF by daboman · · Score: 1

    Considering the problems their web server is having though, here's the link to the technical paper (In PDF Format) so you can skip the website altogether. Singularity PDF

    --
    God, Root, what is difference? -- Pitr from Userfriendly.org
  104. Chuckles by psbrogna · · Score: 1

    Did Windows have this disclaimer when it launched? Or ... yesterday?

    "Again, this is a prototype research OS, not a full fledged OS that can run the typical applications you've come to expect of an OS"
    (from http://channel9.msdn.com/ShowPost.aspx?PostID=6830 2)

  105. Admission of MS guilt? by gambit3 · · Score: 1

    After all... why would you need to focus on dependability....

    unles...

    your current OS wasn't dependable?

    1. Re:Admission of MS guilt? by praxis · · Score: 1

      I'm not talking about whether your conclusion is valid or not, but your argument is flawed. You make the assumption that once a trait has been achieved in a codebase it will remain without effort. I find that assumption incorrect. If I were to write a dependable piece of software today, I would still focus on dependability for the next release. Saying that I am does not imply that I feel I failed in the past.

  106. No relation to VMS October 25 1977 by tengu1sd · · Score: 1
    The concepts of having a program execute in protected unchanging memory is a great new idea. I wonder why no one ever thought of this before. Thank you Microsoft for again defining innnovation to the marketing community.

    Defining a way for SIPs to communicate with communicate between each other, what an incredible idea.

    Reclaiming system resources, I new Microsoft would get around to that eventually.

    /sarcasm

    1. Re:No relation to VMS October 25 1977 by Master+of+Transhuman · · Score: 1


      Microsoft has been claiming system (and user financial) resources since their first OS.

      Oh, wait, you said "re-claiming"...

      That's okay, Microsoft needs to re-claim system resources after the monopoly conviction.

      --
      Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  107. Repeat after me: by Anonymous Coward · · Score: 0

    Black holes do not suck.

    1. Re:Repeat after me: by Fyre2012 · · Score: 0

      correct
      a black hole's ultra-dense mass warps the curvature/fabric of space surrounding it.
      things are not sucked in, they fall in following the curvature of space.

      --
      This is not the greatest .sig in the world, no. This is just a tribute.
  108. Dependable over performance... by HerculesMO · · Score: 1

    So it will DEPENDABLY crash... just takes longer?

    --
    The price is always right if someone else is paying.
  109. Channel 9 interview by Anonymous Coward · · Score: 0

    There's an interview with the two project leads up on Channel 9. You never know they might respond to a Slashdot questionaire.

  110. Relativistic O/S by psbrogna · · Score: 2, Funny

    Perhaps due to time distortion effects, Singularity will reach production before Vista. : )

  111. Hurd vs. Singularity? by sleepingsquirrel · · Score: 1

    Hey, maybe this will get more people interested in the Hurd, since they appear pondering a change to a EROS/Coyotos microkernel thingy.

    1. Re:Hurd vs. Singularity? by iggymanz · · Score: 1

      stole my thunder, was going to say this was Microsoft Hurd. Be a race to see who could release first, MS or GNU, or if the next ice age would start.

    2. Re:Hurd vs. Singularity? by Jesus_666 · · Score: 1

      Great idea. 2027 we'll see announcements that a) Singularity will use Hurd as a foundation to build upon and b) Hurd will use Singularity as a foundation to build upon.

      --
      USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
    3. Re:Hurd vs. Singularity? by The_Dougster · · Score: 1
      Hey, maybe this will get more people interested in the Hurd, since they appear pondering a change to a EROS/Coyotos microkernel thingy.

      Actually, Hurd is moving to the L4 Microkernel. This is (I think) the same kernel used by EROS/Coyotos but I'm not positive. I do know that the Coyotos developers have been contributing to the L4/Hurd project lately, and that they are working on adding some of the features of the latter to the former. Development on the Mach microkernel based Hurd has essentially been dropped as of about 2 years ago.

      I've been a long-time Hurd "interested party" and I actually have the old GnuMach version installed and bootable. I hacked the GNU Pth package to make it compile in Hurd so I could build the Dillo browser and surf the web from Hurd X11 several years ago. I dutifully submitted my patch upstream and it was incorporated into the source :-)

      I periodically compile L4/Hurd and boot it up to see where it's at. I just like fooling around with weird operating systems more than anything. I know enough to be able to compile, install, and boot the things, but I've found I don't know the first thing about kernels from following the L4/Hurd mailing list. Its interesting stuff, but I don't have the CS background to really understand a lot of the concepts being discussed.

      My guess, L4/Hurd might be minimally functional within a year or two on a very limited set of hardware. You can sort of boot it into debug mode now, and the libc is becoming functional slowly, but it's really basic right now.

      --
      Clickety Click ...
    4. Re:Hurd vs. Singularity? by sleepingsquirrel · · Score: 1
      Actually, Hurd is moving to the L4 Microkernel.
      Actually, the Hurd was moving to the L4 kernel. But from what I understand (which isn't much) the team working on L4 has changed emphasis and started working on a new incompatible version called L4sec. So the L4/Hurd team could either fork the current version of L4 (and maintain something that others had lost interest in) or they could port it over to L4sec. But changing to another microkernel means you might as well look around and see what else is available, hence Coyotos.
      This is (I think) the same kernel used by EROS/Coyotos but I'm not positive.
      No. They are two different beasts.
  112. And they are hiring ... by linumax · · Score: 3, Informative

    Maybe a good chance if you are interested!

    We are hiring! If you are interested in a full-time Researcher position, please email a C.V. or resume, a research statement, and the email addresses of three reference letter writers to Galen Hunt. You may also email copies of two publications you feel represent your best work. Minimum education requirement for a Researcher is a Ph.D. in Computer Science or equivalent.

    To facilitate our hiring process, we strongly encourage interested fulltime researcher candidates to submit their application materials as soon as possible and preferably by February 15, 2006.

    In evaluating candidates, we pay particular attention to demonstrated qualities of research taste, innovation, and first-hand system building. We value highly a proven research track record as demonstrated by strong publications in top venues.

    If you are an exceptional Ph.D. candidate interested in a research internship, please use the MSR Internship Application.

    Microsoft is an equal opportunity employer and supports workforce diversity.

    1. Re:And they are hiring ... by Master+of+Transhuman · · Score: 2, Funny

      "Microsoft...supports workforce diversity."

      Yeah, we keep you separate from anybody with a clue. Can't have you getting one.

      That's why we want PhDs with a proven track record of publication in top venues. Got forbid you've ever written a program for a real end user that has to do a real job.

      And no way we want anybody who knows what the words "antitrust" or "truth" means.

      --
      Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  113. Re:It's agood thing and they Should be persuing it by Master+of+Transhuman · · Score: 1


    Yeah, like the Navy ship that launched with much fanfare running Windows NT (no doubt courtesy of some bribes to the Pentagon.)

    Which then went dead in the water and had to be towed back to port.

    Whereas most of the submarine force software was designed by techies and runs on forms of Unix.

    Buy a car that runs on Microsoft software? Hah! No chance. And the only plane I'll fly in that uses Microsoft avionics had better be one with an escape pod on every seat.

    --
    Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  114. not new. Sounds exactly like Ada environement by Anonymous Coward · · Score: 0

    except done in C#.

  115. yes, but... by LordMaxxon · · Score: 1

    ... does it run linux?

    no, of course not, but wouldn't it be great if microsoft (like apple) changed windows to a bsd or other unix core and ported the interface to run on top it?

    1. Re:yes, but... by amliebsch · · Score: 1

      No. Unlike the previous MacOS, there is really nothing wrong with the NT kernel. It is a good core. It's Windows' sup-par shell, userland, and especially third-party device driver code that can be so friggin' annoying/insecure/unreliable.

      --
      If you don't know where you are going, you will wind up somewhere else.
  116. Looks interesting, could lead to a better foundati by pstreck · · Score: 2, Insightful

    After browsing the pdf this os looks very promising. It's implementing a lot of technologies that have to this point only been theorized or tested in very small scale environments. I personally applaud microsoft for taking this initiative on dependenability, for it is something that they have lacked focus on for the past 15 years or so. And i'm honestly kind of disgusted with general microsoft bashing in these comments. Judge technology by it's merits and pitfalls not by it's creators past acheivement, or personal disputes with it's creator. -- nuff said

    --

    Later,
    Phil
  117. When going to RTFA... by christoofar · · Score: 1

    Heh.

    Server Error in '/' Application.
    Runtime Error
    Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

    Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".

  118. Runtime Error by OrangeTide · · Score: 1

    Server Error in '/' Application.
    Runtime Error
    Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

    Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

    <!-- Web.Config Configuration File -->

    <configuration>
            <system.web>
                    <customErrors mode="Off"/>
            </system.web>
    </configuration>

    Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

    <!-- Web.Config Configuration File -->

    <configuration>
            <system.web>
                    <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
            </system.web>
    </configuration>

    --
    “Common sense is not so common.” — Voltaire
  119. And the best part is ... by khasim · · Score: 0, Offtopic

    My posts have not been mod'ed up.

    But the post ranting about "bashing of Microsoft" and how it is "karma whoring" is now +4 insightful (and will probably hit +5).

    Yet that posts contains no specifics regarding Microsoft's contributions.

    1. Re:And the best part is ... by aminorex · · Score: 1

      Because they have a massive astroturf budget, and you don't. So what's new?

      --
      -I like my women like I like my tea: green-
    2. Re:And the best part is ... by devilsadvoc8 · · Score: 1

      Since you are pointing out the modifications to the posts and comparing the "alleged" disparity in comment, you sir, ARE karma whoring.

      --
      B O R I N G
    3. Re:And the best part is ... by Eric604 · · Score: 1

      So what? Specifics regarding Microsoft's contributions are not welcome here, therefore the moderation is correct. Note that insightful/interesting and certainly funny are subjective.

  120. Direct Link to Microsoft PDF by Skier4Life · · Score: 5, Informative
    --


    [SIG] Far better to be thought a fool then to post on /. and remove all doubt.
  121. Someone's already done it.... by Anonymous Coward · · Score: 0

    Someone's already done it. I think they called it "UNIX".

  122. broken already ... by geraint-nz · · Score: 1

    can't be slashdotted already surely, not the great microsoft, for http://research.microsoft.com/os/singularity/ i get the following error message -

    Server Error in '/' Application.
    Runtime Error
    Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

    Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off". ...

  123. division by zero by vlad_petric · · Score: 0, Troll
    We used to say that "Singularity is when God divides by zero". Now it'll be "Singularity is when Bill Gates divides by zero".

    For a lot of M$ drones that consider Bill Gates a god, it won't be that much of a difference

    --

    The Raven

  124. Optimized for reliability, not performance by Junior+J.+Junior+III · · Score: 1

    In other words, it will be a black hole for your processor cycles.

    --
    You see? You see? Your stupid minds! Stupid! Stupid!
  125. Re:Nope. by Brushfireb · · Score: 1

    Whats your point?

    Dictionary.com defines Innovation as "The act of introducing something new." It doesnt need to be completely new or never seen before. 95% of innovation is about building on existing things -- Thats how humanity progresses.

    Most innovation is about finding a new application for an existing idea, or about combining two existing things in a neat and *new* way. Innovation doesnt require completely new ideas, just new applications.

    If we use your definition of innovation, then it rarely, if ever, happens. Every genius, in virtually every field worth mentioning (physics, math, CS, any science, business, economics, politics), is just building upon previous work done in the related subjects.

    Get a grip. MS has done plenty of innovation, and not only in computer science, but also in business, marketing, operations, and HR.

    B

  126. Well at least they admit they won't get performanc by Anonymous Coward · · Score: 0

    Now if they'd admit they won't get good reliability, I'll start believing MS ads.

  127. Actually by Genady · · Score: 1

    Hawking has come out and relented on the whole 'destruction of information' thing with regards to a singularity. Now, he HAS said that any information that you drop into a singularity is munged so badly as to be useless for re-constructing the original information when it comes back out. Oddly, this seems more appropriate for a Microsoft product....

    --


    What if it is just turtles all the way down?
  128. Dependability by RandomPrecision · · Score: 1

    I'm going to rush out and get it because of the description on the website.

    Quote:

    Server Error in '/' Application.
    Runtime Error
    Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

    Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

    <!-- Web.Config Configuration File -->

    <configuration>
            <system.web>
                    <customErrors mode="Off"/>
            </system.web>
    </configuration>

    Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

    <!-- Web.Config Configuration File -->

    <configuration>
            <system.web>
                    <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
            </system.web>
    </configuration>

  129. Yay, 1979 Again! by nate+nice · · Score: 3, Informative

    Have they ever heard of "Non-Stop"? You know, the Tandem kernel? These machines have 99.99% up-time. They don't perform great always but they are bullet proof....and essentially non-hacked because....well, they don't really make root-kits for these things.

    In case you never heard of them, they are a mainframe based computing system that is used heavily in stock markets, banks and ATM devices. Basically in places where up-time and reliability is rather important. I personally don't like programming on them too much (COBOL anyone!..language with no stack...just wrong) but it can be a fun learning experience. At least there is a program called "OSH" that emulates the bash shell, rather poorly I'll admit...but nice for a guy like me anyways.

    I guess a neat thing about Tandem, that also makes them awkward to use initially, is that they don't have a typical file structure. Everything is "Volumes" and you write all these "Servers"....just different. In the end, there is a one-to-one mapping of their file system to something most of us find traditional.

    --
    "If you are a dreamer, a wisher, a liar, A hope-er, a pray-er, a magic bean buyer ..."
  130. WTF by bataras · · Score: 1

    MS singularity? What is that when MS becomes so intelligent it doesn't need human employees anymore?

    1. Re:WTF by Master+of+Transhuman · · Score: 1


      I'd be more interested in what would happen if anybody at Microsoft got intelligent in the first place.

      Probably they'd all quit leaving Bill, Steve and Melinda trying to pack CDs into boxes.

      --
      Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
    2. Re:WTF by Quill_28 · · Score: 1

      Your right, everyone at Microsoft is a complete idiot. ::rolls eyes::

      So glad you are here to clear that up, oh ye of such intelligence!

  131. huge gravitational force by PureCreditor · · Score: 1

    Once your soul is sucked into using Singularity, even a force as strong as Linux cannot pull you out of it

    but then gravity is the weakest of the 4 forces, and a singularity is the apex of gravity, so MS is essentially suggesting their OS is the strongest of the worst?

  132. Re:written from scratch by Anonymous Coward · · Score: 0

    Mac8 OS and its sibling, RTOS (nothing to do with Apple in any form.....)
    uC/OS
    eCos

    oh crap, the list goes on and on.
    Just because it only exists in the embedded world doesn't mean it isn't real

  133. Event Horizon by F.+Bester+Tester · · Score: 1

    It's all relative...

    the farther away you are from anything, the more it appears like a... Singularity!

    I'm betting that that ring0 is inside the advertising event horizon and

  134. Even more FUD by Anonymous Coward · · Score: 0

    MS Research isnt Microsoft. So just like the parent, your post is FUD.

  135. Thank you by Anonymous Coward · · Score: 0

    I've thought about this a lot--what has Microsoft delivered?--and I never could come up with anything that original. If you could provide some more, I would appreciate it.

    As for this study, I was able to look at it several days ago and it doesn't look that original. I remember discussions along those lines when Java was first released--a managed language with enforced usage/constraints(think Ada) is used to write an OS than only runs managed code.

    It's great that they are looking at this because nobody really did anything in this regard but it isn't exactly new.

  136. Device Drivers by miller701 · · Score: 2, Interesting
    While this is still very much a work in progress, the results so far look promising. For example, we have a dynamic web server that uses child processes. Also all of our device drivers run in child processes.

    Does anyone know if this means no restart required after a driver update?

    1. Re:Device Drivers by zootm · · Score: 2, Insightful

      Interesting point! I guess that's exactly what it would mean, yes, since they seem to be treating all of these things at similar levels.

  137. There was a rewrite of OS/2 in... by Karma_fucker_sucker · · Score: 2, Interesting
    progress before Gerstner killed it.

    The rewrite was based on the Mach kernel and it was done for the PPC. It was really nice. It's a shame it was killed - as far I as know. IBM is a huge company and I haven't worked there in 10 years, so take what I've said with a grain of salt or two.

    --
    Evil people don't think they're evil. - George Lucas, Making of Ep III
    1. Re:There was a rewrite of OS/2 in... by Anonymous Coward · · Score: 0

      You are in fact correct, OS/2 for PowerPC was written nearly from scratch (the OS/2 GUI was ported to it) does exist and it is one of the most amazing operating systems ever written. There is an effort underway within IBM and even from a group outside IBM to get that code out. Stay tuned.

    2. Re:There was a rewrite of OS/2 in... by Anonymous Coward · · Score: 0

      See an OS/2 fan's review of OS/2 Power PC edition at this website.

  138. True to Microsoft form by 0xABADC0DA · · Score: 1

    MS Singularity is just their version of jxos - pure Java OS. Their version is actually somewhat worse than jxos, since that at least includes a functional AWT user interface, simple network stack, nfs server, ext filesystem, and minesweeper (you can even try it in vmware, just download the boot disk image). Last I checked singularity had a command-line only interface. It is equivalent to a school project, but that doesn't mean the approach is wrong... it isn't.

    Of course neither are as advanced or usable as Sun's JavaOS... I wish they would open source that! Monolithic unsafe kernels are old hat. They suck in so many ways it isn't even funny.

  139. Longhorn? by Sierpinski · · Score: 1

    Is Longhorn even out yet? I haven't been watching (or do I care) about its release, whether or not its out, or what the date is, because I won't be using it. If it already has been released, then it must be relatively recently. They're already talking about their NEXT operating system? Allow me to say:

    WTF?

    Once, just once, I'd like to see Microsoft release an operating system where they actually PLAN (note it doesn't really have to happen, just planned) for it to be out there for a while? Hasn't the world seen enough of their new and exciting operating systems?

    Yes, this is a troll. Yes, I hate Microsoft. Yes, I'd rather be hacking my 2.6 kernel at home right now.

    1. Re:Longhorn? by amliebsch · · Score: 1

      So, what, they shouldn't research operating system fundamentals until their commercial product is stale? Or would it be okay if they conducted valuable research, as long as they kept it secret and didn't share the results with anybody? What the hell is your problem?

      --
      If you don't know where you are going, you will wind up somewhere else.
    2. Re:Longhorn? by Sierpinski · · Score: 1

      What the hell is your problem?

      My problem is this:

      I'm not talking about waiting until their product is stale. I'm talking about creating a new v3 version before their v2 version is even released.

      I'm all for product updates, especially given the history of security flaws in software (not just Microsoft) but why should they expect people to go out and buy Longhorn when they announce that they're already working on something even newer than Longhorn?

      Quite frankly I don't give a shit how they run their business, because their successes and failures are their problem, not mine. I think it seems stupid to announce the release of the latest and greatest even before their previous version has hit the shelves. I would think for most non-vegetable people, most of which who probably don't NEED the upgrade, they might as well wait until the new one is released, so they're not spending money on a product that will be replaced soon.

      You missed my point, but doesn't really matter to me, because I really just don't care. They make money, they lose money, whatever.

  140. What's in a name? by hunterx11 · · Score: 1

    It's a better name than Pink, at least. Although I suppose if they teamed up with the Apple developers Jobs sacked, you could call it HotPinkOS.

    --
    English is easier said than done.
    1. Re:What's in a name? by cant_get_a_good_nick · · Score: 1

      or taligent... I hate made up names like that.

  141. Stopped reading TFA by DaveM753 · · Score: 1

    As is typical when I read Microsoft articles/publications/press releases, I got to the word "innovation" and stopped reading.

  142. dude, where's my data? by planarian · · Score: 0

    Adds a whole new twist to the black hole information loss debate.

  143. Re:Nope. by SlashSquatch · · Score: 2, Insightful
    Maybe the animosity towards microsoft stems from the feeling of persecution derived from being forced to hard reboot to often (among other ridiculous things). This occuring in stressful situations, coupled with any other quirky behavior, makes the user harbor very negative feelings of being held captive, resulting in frustration, feelings of unproductivity and anger toward the perceived captor. When the captor is a monolithic corporation, incapable of assimilating true user feedback, the feelings are compounded. Slashdot is a healthy release of this animosity.

    "You think your Commodore 64 is really neato What kinda chip you got in there, a Dorito? You're usin' a 286? Don't make me laugh Your Windows boots up in what, a day and a half?"

    --
    Autonomous Retard -- Is your camp safe? UnsafeCamp.com
  144. You actually just defined innovation by Anonymous Coward · · Score: 0

    Innovation is taking old ideas and applying them in new ways. So you just admitted MS innovated that WiFi usage.

  145. Dependability can be achieved many ways by Nom+du+Keyboard · · Score: 1
    designed with emphasis on dependability

    This could mean that it automatically reboots itself for you instead of hanging at the BSOD.

    Personally I prefer the VMware approach that only the virtual machine dies on any non-recoverable error.

    --
    "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
  146. Re:pseudo-academics should be careful what they ba by IdleTime · · Score: 1

    And you have knowledge to evaluate the source code and spot problematic areas or would you have to rely on others and their motivations behind a review?

    I've been using OSS software since way before linux surfaced, got old quarter inch tapes from EUUG in the 80's with software 4 times a year, but I don't think OSS is the holy grail which fixes everything, nor do I think MS is any better than OSS or worse for that matter. For 99.999% of all software users access to the source code is not adding any value to their computing experience nor do they or will they ever have the ability to do anything with that source code. OSS is good for many things, but using this as an argument against another OS which is currently under research seems farflung and downright ridiculous. Besides, the technical paper is quite good and they are definetly on to something, what the endresult will be, we can only speculate about, but I reserve any opinon for the finished product if or when it appears.

    --
    If you mod me down, I *will* introduce you to my sister!
  147. The question is by Mad+Ogre · · Score: 1

    The real question is who owns the intellectual property that the research group comes up with. Since it's MS sponsored, it is MS' baby. Singularity could turn out to be the next OS after Vista. Because, come on, Vista has all the signs of being the next ME. On another note, SUSE 10 has rocked my socks off. I'll stay with that.

    --
    MadOgre.com
  148. screenshot ! by Anonymous Coward · · Score: 0
  149. Re:Nope. by Anonymous Coward · · Score: 0

    The problem is that Microsoft's marketing (to include it's top Officers) would have you believe that their "innovation" is unique. That they do things that nobody else does.... or can do. Not to mention their statement that Microsoft is needed because methods like Open Source creates no innovation.

    There are legislaters and so-called IT professionals who buy this; nothing exists before Microsoft does it. You see it on Slashdot all the time. In every "Microsoft innovation" thread, you will have a number of individuals providing examples of Microsoft "innovation" that are either entirely incorrect or debatable. And while I find the Professionals believing this sad... it is the legislaters that really worry me.

    Note that this is an entirely different discussion from whether Microsoft makes good products. The issue isn't whether you find Microsoft products easier to use... better for your needs... worth the money... or whatever. The question you should ask yourself is where would we be today without Microsoft.

    The fact is, Microsoft does what everyone else does. They're in the computer science business. They build on the work of others. And that's how things move along. The difference is that others seem to recognize this. Heck - Open Source methodology is all about it. Microsoft would rather you not look behind that curtain.

    And that's why Microsoft critics get hung up on the whole "innovation" issue.

  150. What is so new and innovative about it? by soaro77 · · Score: 1

    What is so new and innovative about this? Java has been doing this for 10 years.

  151. Re:Looks interesting, could lead to a better found by jcarter · · Score: 1

    Like the parent, I read the PDF writeup (linked to from the story page), and got kind of eager to see and play with this.

    I think this issue is that Microsoft is so large that it's becoming a sort of confederation of departments (though an analogy with a more totalitarian feel might be better), in which each part is by orgizational necessity granted a degree of autonomy. Also, with a company this big, I don't think you can truly speak of one, overarching "Microsoft Culture" to be found in all departments of the company.

    I predict a movement of the "Microsoft as a whole still sucks, but Their Reasearch department is doing some *cool* stuff" variety in coming times.

    Just my 0.0167 EUR

  152. MS Innovation by Anonymous Coward · · Score: 0

    Such as what, specifically?

    Here's an example: Lie, cheat, break laws, repeat until you have $40 billion in the bank.

    Done.

  153. Let's try reliability one more time... by Minwee · · Score: 1
    As I recall the last time they did something like this they called it "Windows NT 3.5". It didn't do so well because the customers complained about how they wanted performance more than reliability so it was sent back to the spawning pits to be beaten into "Windows NT 4.0".

    The rest, as they say, is history. Or marketing. Whichever.

  154. IE it's an interpreter by spitzak · · Score: 1

    Anybody questioning how this is done has not realized the the "program" is interpreted byte code, not any kind of present day machine language. The interpreter (assummed to have no bugs itself) is incapable of writing over memory not owned by the current process.

  155. Yup... by GoGoGadgetFeet · · Score: 1

    "...it is impossible to predict how a singularity will affect objects in its causal future." - NCSA Cyberia Glossary

    Sounds like a Microsoft operating system alright...

  156. not new, but maybe what the industry needs by idlake · · Score: 1

    It's good that, after a 20 year hiatus, people are starting to write operating systems in languages again that are a bit saner than C.

    While not new, maybe this will spur on others to start similar efforts. We really need a successor to Linux and BSD, something with runtime safety and garbage collection in the kernel.

    1. Re:not new, but maybe what the industry needs by joto · · Score: 1
      Garbage collection in the kernel is a stupid idea. Whenever you make a garbage collector implementation, it's tailored to a specific language, and a specific usage pattern.

      E.g. a stack-based language would need a GC that needs how to scan the stack for pointers. But a stackless language may use the stack register as a general purpose register, and couldn't use the same implementation.

      And even different stack-based languages, might use different layouts of the stack, meaning they either need different garbage collectors, an overly general parametrized garbage collector, or that they all need to be forced to use the same layout.

      Different languages also use different object layouts. Some might tag all their objects with the information necessary for the GC. Others would need to rely on other static or dynamic guarantees about object layout. And even if we limit ourselves to fully tagged objects, a kernel based GC would need to force a particular way to tag them, something that again could force a certain object model onto every language.

      There is also the very important difference between a stop-the-world collector, and a realtime GC. And if you want the collector to handle threads, you have yet another difference (actually the details here are really nasty). Are you mostly allocating short-lived objects, or long-lived? Does your heap size remain relatively constant, or does it grow and shrink a lot? Is your program short-lived, or is it long-lived? Do you worry more about fragmentation or about memory-locality of objects created in the same time-frame?

      The list of policy decisions to make in a garbage collector is nearly endless. Each garbage collector must be tuned to the particular language it's intended for, and even then, there are usually different garbage collectors for different types of programs written in the language. Putting a GC in the kernel forces the same policy-decisions onto everyone, and I fail to see any benefit in that!

    2. Re:not new, but maybe what the industry needs by idlake · · Score: 1

      Garbage collection in the kernel is a stupid idea. Whenever you make a garbage collector implementation, it's tailored to a specific language, and a specific usage pattern.

      Even if those statements weren't utter nonsense, I suggest you enumerate the languages that I can currently write kernel code in. Well, let's see: C, and ...? Oh, there is nothing else. What about a CLR-based kernel? Wow, I can write kernel modules in C, C++, Java, C#, Basic, Oberon, Eiffel, F#, OCAML, Prolog, Smalltalk, Python, and probably a lot more.

      Of course, user mode software can be written in any language.

      Putting a GC in the kernel forces the same policy-decisions onto everyone, and I fail to see any benefit in that!

      A kernel GC only collects kernel data structures, more efficiently and reliably than anything you could do by hand. But if you like, you can still adopt whatever inefficient manual policies you want to implement, both for kernel and for user code.

    3. Re:not new, but maybe what the industry needs by joto · · Score: 1
      Ah, you want a GC for the kernel. That's an entirely different thing, and not stupid at all. Even in linux, some data-structures are garbage-collected. What I objected to was making GC a kernel service that userspace programs could use. And believe me or not, I've seen people argue for this at numerous places, most of which, the people arguing for it should know better (unless what they *really* want is to take the kernel away, and have all applications written in a single, safe language with a certified compiler, e.g some ML-variant).

      By the way, there's nothing forcing you to use C for kernel code. You are free to write your own OS kernel in whatever language you like, and many people have done so (including microsoft research). Even if you want to write linux kernel code, there's nothing forcing you to use C, as long as you can link it with gcc. You can use C++, Pascal, Ada, Fortran, Objective C, Java, or anything else gcc has a frontend for. Or you can use some other language, as long as you find a way to link your runtime environment, and some ffi-hooks into the kernel. It's only if you ever want your code accepted by linus, that you need to stay within C-land.

  157. Huh? by Anonymous Coward · · Score: 0

    If Apple had purchased BeOS then the first thing they would have done is redesign the interface to conform to their interface guidelines--BeOS is a better example of violating Fitt's law than Windows ever was.

    And then there are those outstanding, intermittent locking/race-condition bugs that were discussed by former BeOS engineers--the implication being that widespread usage would have made them less intermittent and a nightmare to deal with.

  158. Cosmology by gmuslera · · Score: 1

    If we travel deep deep into all the Microsoft vaporware, we will find an all-resource sucking Singularity. My best bet is that that codename will be the kernel and the box will have a "Galaxy" brand (after all, is what you see high in the sky when you look beyond your window).

    1. Re:Cosmology by praxis · · Score: 1

      When it is not announce as product, it's not really vaporware. It's not even a ware. Do you even know what Microsoft Research is and what they do?

  159. Abject failure to perform by Baldrson · · Score: 0, Flamebait
    Expressive, safe programming languages, such as Java and C#.

    First of all, safe is implied by expressive. Side-effects like buffer overflows result from the language semantics not being expressive. For example, you virtually never intend for an array allocation to result in an object whose semantics are to walk all over other data structures that happen to have been declared in proximity.

    Secondly, with that fact firmly in mind, you want to focus on expressivity so that your language helps you say precisely what you mean -- and you never mean "crash or open up security holes due to random interactions".

    These guys really think Java and C# are "expressive" when it comes to programmer intent?

    What abject failure to perform their duty!

  160. UNIX Inspired by Anonymous Coward · · Score: 0

    I was looking through some of the PDFs available on their website. It appears that Microsoft is doing something they haven't done in a long time, by incorporating some very UNIXish qualities into this operating system. From /dev device nodes, to a single / based filesystem hierarchy (with mountpoints), to UNIX style network ports ("/tcp/128.0.0.1/80"), to "Access Control Expressions" (a kinda cool extension to ACLs).......They claim this operating system is designed uniquely from the grounds up, but there's no arguing with the fact that UNIX just does some things *right*.

  161. apples and oranges by idlake · · Score: 4, Interesting

    The two are very different beasts.

    EROS uses C and relies on memory management hardware for isolation. EROS also can't analyze or verify code it loads.

    Singularity uses C# and does not use memory management hardware for protection; it guarantees isolation via runtime checks, and it can perform extensive code analysis on load.

    I don't know whether Singularity is going to make it, but I have used and developed on systems like it (the idea isn't new), and it is a lot nicer than either UNIX kernels or EROS-like kernels.

    1. Re:apples and oranges by naasking · · Score: 2, Insightful

      EROS uses C and relies on memory management hardware for isolation. EROS also can't analyze or verify code it loads.

      I don't want to re-hash our previous argument on this subject, but the above statement is trivially falsifiable. Singularity is built on a microkernel. EROS is built on a microkernel. Anything that can be built on Singularity, can be built on EROS, including verifiers, virtual machines, Software Isolated Processes, etc.

      EROS has a default mechanism for isolating faults and loading untrusted code in the absence of any safety guarantees: the constructor.

      I don't know whether Singularity is going to make it, but I have used and developed on systems like it (the idea isn't new), and it is a lot nicer than either UNIX kernels or EROS-like kernels.

      Not that you know what developing on an EROS-like system is like, considering it's a completely revolutionary architecture comparable only to KeyKOS from which it's derived.

    2. Re:apples and oranges by Salamander · · Score: 1
      I don't want to re-hash our previous argument on this subject, but the above statement is trivially falsifiable. Singularity is built on a microkernel. EROS is built on a microkernel. Anything that can be built on Singularity, can be built on EROS, including verifiers, virtual machines, Software Isolated Processes, etc. EROS has a default mechanism for isolating faults and loading untrusted code in the absence of any safety guarantees: the constructor.

      I was also involved in that previous discussion (in fact your post there was spawned by one of mine) and I think idlake is on the right side this time. The EROS architecture still relies on hardware memory protection between processes, which is a fundamentally different paradigm than a single-address-space OS that uses either compile-time or load-time verification to guarantee safety. In addition, the EROS contructor does not provide any of the higher-level guarantees (e.g. regarding invalid state transitions) that Sing# does via the "Boogie" verifier. Yes, you could build all the important parts of Singularity in EROS (and vice versa) but the result would be more of a emulation or virtualization like User-Mode Linux than like a single OS. The hooks just aren't there to fuse the two approaches into a coherent whole. There's nothing wrong with EROS, and there's nothing wrong with Singularity. They can both help us learn different things. Pissing contests about which one trumps the other are just pointless and childish.

      --
      Slashdot - News for Herds. Stuff that Splatters.
    3. Re:apples and oranges by idlake · · Score: 1

      but the above statement is trivially falsifiable. Singularity is built on a microkernel. EROS is built on a microkernel. Anything that can be built on Singularity, can be built on EROS, including verifiers, virtual machines, Software Isolated Processes, etc.

      Whether or not you call the two systems "microkernels", they are different designs and use very different runtimes. You can implement the same architectural features in both, but that's like saying that you can implement anything in assembly that you can implement in Perl--it's just not an interesting statement.

      EROS has a default mechanism for isolating faults and loading untrusted code in the absence of any safety guarantees: the constructor.

      And you do a context switch on every method call? C# and Java guarantee fault isolation at the level of the individual programming language object, there is nothing like it in any C-based system. C# and Java also allow you to get information about the type and structure of every single allocated block of storage; try that in a C runtime.

      Not that you know what developing on an EROS-like system is like, considering it's a completely revolutionary architecture comparable only to KeyKOS from which it's derived.

      The architecture isn't at issue, at issue is developing kernel modules in an unsafe language without reflection, without class loaders, and without garbage collection.

    4. Re:apples and oranges by Salamander · · Score: 1
      at issue is developing kernel modules in an unsafe language without reflection, without class loaders, and without garbage collection.

      In Singularity, class loaders are essentially [i]verboten[/i], reflection is compile-time, and garbage collection isn't what you're used to either. Furthermore, they run fully native code, not interpreted or JIT-compiled. In fact, they do a pretty good job of proving you wrong on just about every point you made in the previous thread, so maybe you shouldn't be trying to cite their experience as support for your still-broken ideas about OS design.

      --
      Slashdot - News for Herds. Stuff that Splatters.
    5. Re:apples and oranges by cartman · · Score: 3, Insightful
      Singularity is built on a microkernel. EROS is built on a microkernel.
      You completely misunderstood the point of Singularity. The point of Singularity is that all code (except OS code) is subject to verification, and any code that isn't verifiable is runtime bounds-checked. Furthermore, in Singularity, inter-process communication is structured, such that the OS can verify IPC traffic. Furthermore, the languages for Singularity are strongly typed at the object code level, and garbage collection is performed by the OS--explicit deallocation is impossible for any application. These facilities make it impossible for any application to have buffer overruns, segfaults, or overruns of other apps' data--as a result, all applications can run in ring 0 and virtual memory is not required.

      All that has nothing whatsoever to do with Eros. The two projects are not even similar.

      Of course a verifier could be written as an application for Eros (or for DOS, for that matter). That statement is like saying that C++ is no different from assembly, because they're both built atop similar hardware and can be used to implement the same things.

      Not that you know what developing on an EROS-like system is like, considering it's a completely revolutionary architecture comparable only to KeyKOS from which it's derived.
      The Coyotos OS is based on Eros and is quite similar. Additionally, Eros is not completely revolutionary. From the eros web page, What's new about Eros?: "Each of these faclities is...essential to providing scalable reliability, and all of them have appeared in prior systems. No prior system, however, has ... this particular combination ... in quite the same way.".
      Not that you know what developing on an EROS-like system is like
      Your arrogance is unjustified.
    6. Re:apples and oranges by idlake · · Score: 1

      In Singularity, class loaders are essentially [i]verboten[/i], reflection is compile-time, and garbage collection isn't what you're used to either.

      That's all be true, but it doesn't contradict what I said.

      In fact, they do a pretty good job of proving you wrong on just about every point you made in the previous thread, so maybe you shouldn't be trying to cite their experience as support for your still-broken ideas about OS design.

      I used Singularity only to illustrate one point, namely that fault isolation using a safe language with a well-designed type system is a direction we should be going into, as opposed to using an unsafe language with or without memory management hardware.

      You are right that, beyond that, the developers of Singularity have some architectural ideas similar to those in Eros and I consider those aspects of the systems to be equally spurious and unproven. Of course, from your postings, it is evident that your emphasis is the opposite: you view the specific fault isolation mechanism as an unimportant implementation detail and think that the architectural ideas are what matters.

      And the fact that you think that a tech report about a half-finished implementation constitutes "proof" of any form illustrates a fundamental problem with operating systems architecture research: it's still all a bunch of handwaving. But until OS researchers get their act together methodologically, at least they should develop the kernels with safer languages and runtimes so that the rest of us can get our work done better. The architectural gimmicks you add, we can easily ignore, like we have for the last half century.

    7. Re:apples and oranges by Salamander · · Score: 1
      from your postings, it is evident that your emphasis is the opposite: you view the specific fault isolation mechanism as an unimportant implementation detail and think that the architectural ideas are what matters.

      Actually, any rational person who looked at my postings either in this thread or on my own site would come away with the exact opposite impression. I think fault-isolation mechanisms are a very important aspect of OS design, which is why your idea of running an interpreted or JIT-compiled language in the kernel is ridiculous. The performance and complexity implications are simply unacceptable.

      the fact that you think that a tech report about a half-finished implementation constitutes "proof" of any form illustrates a fundamental problem with operating systems architecture research: it's still all a bunch of handwaving

      The very fact that you don't realize when your own arguments have been disproven shows that you're the one doing the handwaving - but it could hardly be any other way when you're commenting on a domain where you've never done any actual work. You claimed that microkernels had to be based on hardware protection; Singularity is clearly a microkernel and everyone recognizes it as such but it has no such dependency. You assumed that a complex runtime is the only way to maintain language safety guarantees; Sing# and SIPs prove you wrong. I've been very clear that the progress on Singularity so far doesn't prove that they've found the One Best Way to write an OS, but they have done enough experiments and provided enough analysis to disprove your claims and assumptions. You're simply full of shit when it comes to operating systems, idlake. Stick to whatever it is that you know, which seems to be very little, and let the grownups do the real work.

      --
      Slashdot - News for Herds. Stuff that Splatters.
    8. Re:apples and oranges by naasking · · Score: 1

      I was also involved in that previous discussion (in fact your post there was spawned by one of mine) and I think idlake is on the right side this time.

      In the right? I never countered any of idlake's claims other than the false ones, namely that such functionality cannot be had in other properly designed microkernel systems (of which EROS is one).

      The EROS architecture still relies on hardware memory protection between processes, which is a fundamentally different paradigm than a single-address-space OS that uses either compile-time or load-time verification to guarantee safety.

      Singularity is not a single address space OS.

      In addition, the EROS contructor does not provide any of the higher-level guarantees (e.g. regarding invalid state transitions) that Sing# does via the "Boogie" verifier.

      What do you consider an "invalid state transition"? From which perspective? The EROS kernel, due to its atomic design, ensures that each state following a message send is correct given the previous state was correct from the kernel's perspective. From the application perspective, if it contains an algorithmic error, the state transition may trigger a bug, so a message may induce an incorrect state transition. There is nothing a verifier can do to prevent this. Only a system programmed fully with verification proofs can make guarantees about total correctness in the face of changing state.

      Yes, you could build all the important parts of Singularity in EROS (and vice versa) but the result would be more of a emulation or virtualization like User-Mode Linux than like a single OS.

      This is the nature of computation. Xen is a "virtual machine monitor" which is really just a microkernel (or exokernel if you prefer). Does running any operating atop Xen make it any less of an operating system? There is no difference between "emulation" and "execution". The distinction is artificial and does not exist. Just because the code executed in Singularity is MSIL and not the native instruction set, does that make it "not a real operating system because its emulated"?

      There's nothing wrong with EROS, and there's nothing wrong with Singularity. They can both help us learn different things. Pissing contests about which one trumps the other are just pointless and childish.

      I agree. Siungularity looks very cool. But if someone makes an incorrect statement, I will correct them. I would expect nothing less.

    9. Re:apples and oranges by naasking · · Score: 1

      You completely misunderstood the point of Singularity. The point of Singularity is that all code (except OS code) is subject to verification, and any code that isn't verifiable is runtime bounds-checked.

      No I really didn't. There is no reason you cannot build this functionality on EROS. Which was my point that you seemed to have missed. We have this functionality running on Linux right now with Java, mono, etc.

      Furthermore, in Singularity, inter-process communication is structured, such that the OS can verify IPC traffic.

      All IPC is structured to a certain extent, particularly in microkernels. Furthermore, why should the OS care how an IPC data string is structured? This is a contract between communicating entities. This is specified in typical microkernel systems like L4 and EROS via IDL. This is implemented in Singularity via their strong interface contracts (which is just another IDL). This is not a revolutionary idea and is not among the true benefits that Singularity provides.

      Furthermore, the languages for Singularity are strongly typed at the object code level, and garbage collection is performed by the OS--explicit deallocation is impossible for any application. These facilities make it impossible for any application to have buffer overruns, segfaults, or overruns of other apps' data

      These are all guarantees you can have in any other OS. Other microkernels merely use the MMU to enforce isolation instead. That's the only difference between EROS and Singularity in this regard, and again, it's not among the main benefits Singularity provides.

      All that has nothing whatsoever to do with Eros. The two projects are not even similar.

      Sure they are. They both seek to create a secure, reliable operating system. Comparing them on the techniques they use to accomplish those ends is perfectly valid.

      The Coyotos OS is based on Eros and is quite similar.

      Coyotos is being developed by the EROS creators. I'm on the development mailing list for both. I'm very familiar with these projects.

      Additionally, Eros is not completely revolutionary. From the eros web page, What's new about Eros?: "Each of these faclities is...essential to providing scalable reliability, and all of them have appeared in prior systems. No prior system, however, has ... this particular combination ... in quite the same way.".

      To truly understand the impact of such a statement, I think you should read into EROS. Using the same logic, Java and .NET were nothing revolutionary, and yet they transformed an entire software industry, and it is driving this new operating system which everyone thinks is the cat's pyjamas. Sure EROS is not the first capability-based system, sure it's not the first microkernel, sure its not the first system with a coherent single-level storage model, but it provides all of these features, and then some. It started as a re-implementation of KeyKOS, and grew into its own beast.

      Your arrogance is unjustified.

      I'm sorry, but if you read the previous thread where idlake and I argued, you'll see that my supposed "arrogance" is quite justified. Though how you can classify a simple statement of fact (that idlake has not programmed on anything even remotely resembling EROS) with arrogance is beyond me.

    10. Re:apples and oranges by Salamander · · Score: 1
      Singularity is not a single address space OS.

      Look again. SIPs are explicitly defined as "closed object spaces, not separate address spaces" that "do not rely on memory management hardware for isolation."

      From the application perspective, if it contains an algorithmic error, the state transition may trigger a bug, so a message may induce an incorrect state transition. There is nothing a verifier can do to prevent this.

      Look again, this time at the section on Sing# and Boogie which do plenty to prevent this.

      f someone makes an incorrect statement, I will correct them. I would expect nothing less.

      You're welcome.

      --
      Slashdot - News for Herds. Stuff that Splatters.
    11. Re:apples and oranges by naasking · · Score: 1

      Whether or not you call the two systems "microkernels", they are different designs and use very different runtimes. You can implement the same architectural features in both, but that's like saying that you can implement anything in assembly that you can implement in Perl--it's just not an interesting statement.

      But it's a true statement. Your original statement that EROS cannot provide these same guarantees was simply false. I merely pointed it out, nothing more.

      And you do a context switch on every method call?

      You don't perform a context switch on every method call in any language. The performance is simply prohibitive.

      C# and Java guarantee fault isolation at the level of the individual programming language object, there is nothing like it in any C-based system. C# and Java also allow you to get information about the type and structure of every single allocated block of storage; try that in a C runtime.

      There is nothing stoping you from programming each EROS process in C#, Java, or any other language which provide these same features. You are way too fixated on the fact that the EROS core is written in C. That has little to no bearing on what I was pointing out. I am not a C fanboy, nor am I saying a system should be programmed in C. Stop attacking strawman arguments.

      The architecture isn't at issue, at issue is developing kernel modules in an unsafe language without reflection, without class loaders, and without garbage collection.

      This and your original statement are still incorrect. Firstly the OS "architecture" is fundamental to how you program in these systems. Secondly, there is no such thing as a "kernel module" in either Singularity or EROS. There are only Software Isolated Processes and user-level processes respectively. Communication between these isolated object pools is accomplished via IPC. In Singularity and EROS, the IPC is specified via a strong interface contract which is an IDL; or you can can program the marshalling and unmarshalling of data manually in EROS if you like, but who wants to do that?

      Thirdly, there is nothing preventing you from implementing anything in a higher-level language in EROS, except the realities of system programming. For example, try writing a disk driver backed by Singularity's runtime features, on a system that is fully loaded and swapping. The disk driver tries to allocate memory, a page must be swapped to free a frame for the driver, this is converted into a request to the disk driver to write the page to disk, but oops! the driver is waiting for memory and can't proceed.

      Some system software and application software simply must be programmed fundamentally differently. My earlier assertions are that full control over runtime features is necessary in these scenarios, as my example illustrates.

    12. Re:apples and oranges by naasking · · Score: 1
      Look again, this time at the section on Sing# and Boogie which do plenty to prevent this.

      From Section 4.8:
      Verifying that code executed in Singularity is type safe and satisfies the memory independence invariants is a three-stage process. The Sing# compiler checks type safety, ownership rules, and protocol conformance during compilation. The Singularity verifier checks these same properties on the generated MSIL code. Finally, the back-end compiler should--but does not as yet--produce a form of typed assembly language that enables these properties to be checked yet again by the operating system.
      Type and memory safety are the only guarantees. These go a long way sure, but they do not prevent algorithmic errors.
    13. Re:apples and oranges by Salamander · · Score: 1
      Type and memory safety are the only guarantees.

      Look again at what you just quoted. Here, I'll even help you by highlighting the part you obviously skipped over.

      The Sing# compiler checks type safety, ownership rules, and protocol conformance during compilation.

      What do you suppose "protocol conformance" means? It means avoidance of exactly the kind of invalid state transition that we've been talking about. Your claim that "there is nothing a verifier can do to prevent this" is clearly false since the verifier can and does prevent the module from compiling if it contains such errors. Likewise, while the safety guarantees are by no means complete (I've already pointed out the lack of coverage for both livelock/deadlock and indefinite postponement as a result of component failure in posts here and on my website), there are clearly some guarantees beyond type and memory safety so your statement above is also false.

      You're letting bias get in the way of understanding what you're looking at, naasking. Please take off the EROS-colored glasses for a moment and actually look at what Singularity is doing instead of just trying to mine the document for quotes that you (wrongly) think support your predetermined position.

      --
      Slashdot - News for Herds. Stuff that Splatters.
    14. Re:apples and oranges by naasking · · Score: 1
      What do you suppose "protocol conformance" means? It means avoidance of exactly the kind of invalid state transition that we've been talking about. Your claim that "there is nothing a verifier can do to prevent this" is clearly false since the verifier can and does prevent the module from compiling if it contains such errors.

      I say "algorithmic errors". You say "protocol errors". We are not saying the same thing. Example: a SIP receives an HTTP GET request. It incorrectly parses it as an HTTP DELETE request. Is the verifier going to catch that? This is an algorithmic (programming) error. In the absence of a proof system that understands the HTTP protocol, a verifier/compiler will not be able to catch these sorts of bugs. In certain circumstances, you can attempt to express the solution in such a way that the type system might be able to catch this sort of error. You cannot do this for all problems.

      You're letting bias get in the way of understanding what you're looking at, naasking. Please take off the EROS-colored glasses for a moment and actually look at what Singularity is doing instead of just trying to mine the document for quotes that you (wrongly) think support your predetermined position.

      1. You seem to suffer from the very problem you accuse me of, as your implication of EROS-coloured glasses demonstrates. This particular discussion is not about EROS and nowhere did I drag EROS into it (except in addressing the original EROS claim). Instead of attempting to divine my state of mind, please just stick to addressing the facts.
      2. I asked you two posts ago to define "invalid state transition" so that we could have a common understanding with which we could analyze how Singularity prevents it and other systems do not. I'm still waiting. All disagreements so far have stemmed from this lack of common basis.
      3. I'm confused why you would consider citing quotes from the actual source a bad thing. It's my understanding that it actually clarifies the discussion, as this exchange just demonstrated.
    15. Re:apples and oranges by Salamander · · Score: 1
      I say "algorithmic errors". You say "protocol errors". We are not saying the same thing. Example: a SIP receives an HTTP GET request. It incorrectly parses it as an HTTP DELETE request. Is the verifier going to catch that? This is an algorithmic (programming) error. In the absence of a proof system that understands the HTTP protocol, a verifier/compiler will not be able to catch these sorts of bugs.

      So unless the verifier can catch all algorithmic errors, it's worthless? Bullshit. You said type and memory safety were the only guarantees. Key word: only. A single existence proof is sufficient to refute that, and that existence proof is right in the paper. What is meant by protocol error is also quite clear from the paper - it's a protocol between components in the system (not one handled externally like HTTP) expressed as state transitions forming a channel contract. It really is right in there. It's what distinguishes Sing# from Spec#. The verifier can catch those errors, and the fact that it's a subset of all algorithmic errors is a red herring. Your statement remains false.

      nowhere did I drag EROS into it (except in addressing the original EROS claim)

      ...and that doesn't count because...? Oh, because it's not convenient for you. Because disavowing it, however speciously, gives you an opportunity to play "I'm rubber, you're glue" games. Grow up.

      I asked you two posts ago to define "invalid state transition" so that we could have a common understanding

      Read the damn paper. They're very clear about what they're referring to...oh, forget it. You obviously won't accept anything that undermines your position unless you have no choice, so I refer you to the description of channel contracts on page 15 of the document:

      a contract specifies the allowable message interactions via a state machine driven by send and receive actions

      A send and receive action inconsistent with this state machine is therefore quite obviously an invalid state transition. Should I define "state" and "transition" for you now, or is that enough?

      I'm confused why you would consider citing quotes from the actual source a bad thing.

      Quoting a source in good faith is a good thing. Selectively quoting or misquoting is not. Clear enough?

      --
      Slashdot - News for Herds. Stuff that Splatters.
    16. Re:apples and oranges by naasking · · Score: 1
      So unless the verifier can catch all algorithmic errors, it's worthless? Bullshit.

      I never said any such thing. Slashdot posters are really big fans of the strawman aren't they? Word of advice, before replying, take a deep breath, relax, and read carefully.

      What is meant by protocol error is also quite clear from the paper - it's a protocol between components in the system (not one handled externally like HTTP) expressed as state transitions forming a channel contract. It really is right in there. It's what distinguishes Sing# from Spec#. The verifier can catch those errors, and the fact that it's a subset of all algorithmic errors is a red herring. Your statement remains false.

      No, it really doesn't. Let's review. Here is the original statement I made which you disagreed with:
      From the application perspective, if it contains an algorithmic error, the state transition may trigger a bug, so a message may induce an incorrect state transition. There is nothing a verifier can do to prevent this.
      This statement is predicated on a particular definition of "state transition". This is why I asked for your definition of "state transition" to compare to mine, and why I qualified it from different perspectives (application, kernel, etc.). The original statement stands: an application can indeed be left in an "invalid state" following a communication and the verifier cannot catch these sorts of bugs. In fact, immediately following that original statement I clarified:
      Only a system programmed fully with verification proofs can make guarantees about total correctness in the face of changing state.
      Yet, you quoted the original statement in "bad faith" ignoring this clarification which makes it quite clear where I'm coming from. So instead of answering the question and fruitfully advancing this discussion, you chose to attack a strawman.

      So, now we're getting somewhere: what the verifier does buy you, is that the message input and output sequence is explicitly enumerated and the verifier ensures that the exit points of the code dispatched on these messages return the expected reply message types. Right?

      Finally, perhaps you can clarify what you mean by HTTP being an "external protocol". Do you only mean that it does not use the platform's built-in protocol mechanisms? Hate to break it to you, but most of the world is composed of protocols of this nature.

      You said type and memory safety were the only guarantees. Key word: only.

      Because I did not see the relevance of "protocol" to "algorithmic correctness" as I was arguing it.

      ...and that doesn't count because...? Oh, because it's not convenient for you. Because disavowing it, however speciously, gives you an opportunity to play "I'm rubber, you're glue" games. Grow up.

      I didn't bring EROS up, I merely corrected an error. Once corrected, I did not drag EROS into anything. You are dragging it in now. Really, it's not that hard to understand.

      Quoting a source in good faith is a good thing. Selectively quoting or misquoting is not. Clear enough?

      Should I have quoted the entire paper? I'm sure you agree that every quote is a selective quote. I copied and pasted the text verbatim from the paper, so I didn't misquote. Please, clarify exactly what about my quote was in "bad faith".
    17. Re:apples and oranges by Salamander · · Score: 1
      The original statement stands: an application can indeed be left in an "invalid state" following a communication and the verifier cannot catch these sorts of bugs.

      Wrong again. It cannot catch all of these sorts of bugs, and nobody has said that it could. I even provided some counterexamples four days before this thread started. Your statement, though, was that a verifier can do nothing about such bugs. "Nothing" is an absolute negation. Since you're being such an ass about this, I'll reduce it to purely logical terms. Let X be the set of algorithmic errors, Y the subset of protocol errors (according to the definition used by myself and the Singularity team), and Z the set of errors that can be caught by a verifier. Your statement was that the intersection of X and Z is empty - not small, but empty. The Singularity paper shows that the set of Y and Z is not empty. Because Y is a subset of X, that means your claim must be false. It doesn't matter one bit whether there are bugs that are members of X but not Z, i.e. other kinds of algorithmic errors. No matter how many times you come back to it, that remains a red herring.

      Only a system programmed fully with verification proofs can make guarantees about total correctness in the face of changing state.

      That is not in dispute but, again, you are confusing "not all" with "none" and are guilty of moving the goalposts. We're not talking all or nothing; we're talking about zero vs. non-zero.

      perhaps you can clarify what you mean by HTTP being an "external protocol". Do you only mean that it does not use the platform's built-in protocol mechanisms? Hate to break it to you, but most of the world is composed of protocols of this nature.

      Either you're the stupidest person on Slashdot (quite an achievement) or you're playing dumb to red herring to distract from your previous dishonesty. An external protocol is, quite obviously, one that is used to communicate with an external entity - i.e. on another box, running a different OS image, accessed via an external network interface. You can look on the back of your machine and see one of those if you're still confused. The world is not, in fact, composed only of such protocols, but many think so because they generally only hear the word used in that context. What you're unaware of is that there are protocols running within your system as well. There are CPU/memory-bus protocols and I/O-bus protocols which can actually be quite complex and are often studied using the exact same tools as are used for the more familiar kind of network protocols. There are also protocols within software that are often not recognized as such but can be treated that way for purposes of verification. "Call open() to get a file descriptor and then pass that to read()" is a protocol, and automated tools can check e.g. that you don't call read() before calling open() or free() before calling malloc() etc. almost ad infinitum. Protocols are actually all around you, and only your own narrowness of vision prevents you from seeing that.

      I'm sure you agree that every quote is a selective quote.

      It's selective in the sense of argument by selective observation. I realize you're not fluent in English, but please at least try to understand people before you disagree with them.

      --
      Slashdot - News for Herds. Stuff that Splatters.
    18. Re:apples and oranges by naasking · · Score: 1

      Either you're the stupidest person on Slashdot (quite an achievement) or you're playing dumb to red herring to distract from your previous dishonesty. [...] Protocols are actually all around you, and only your own narrowness of vision prevents you from seeing that.

      Ad-hominem attacks do not add credibility to your arguments FYI. And as I said earlier, please avoid trying to divine my state of mind; you know nothing about me, and every personal attack you make and every strawman you propose just makes you look more ignorant and childish. You can presume I'm deliberately antagonizing you or you can presume that we're having a strictly intellectual disagreement or perhaps a misunderstanding. Personally, I prefer to stick to the facts. Your call. That's the last I'll say on the matter.

      Wrong again. It cannot catch all of these sorts of bugs, and nobody has said that it could. [...] Your statement, though, was that a verifier can do nothing about such bugs.

      Which bugs are "such bugs"? You are classifying "algorithmic" bugs as the superset of all types of bugs ("I'll reduce it to purely logical terms. Let X be the set of algorithmic errors, Y the subset of protocol errors"). In the Church-Turing sense of "algorithm" word your use might be correct (although some people disagree), but you're completely ignoring the constraints I placed on my original, specific use of the word. The verifier ensures the correct sequence of requests/responses via endpoints, but it says nothing about the application's internal state.

      You can accuse me of "moving the goal posts" all you like, but that statement is perfectly consistent with every statement I've made then and since. That statement is still true. Now that we've agreed on what was meant by "state transitions" (ie. being specific to the protocol state machine), it is largely orthogonal to my original concerns. Or as you would say, X (my constrained "algorithmic" bugs) and Y (protocol bugs) are disjoint sets.

      Returning to my original example, a web server which incorrectly dispatches to a POST handler on a GET request has performed an invalid application state transition, even though the protocol state transition was valid. My original statement, stands: the verifier can do nothing about this sort of bug. You seem to be having difficulty understanding that right from the outset we weren't quite on the same page. Hence why I asked you to define "state transition". Then you accuse me of "moving the goalposts", instead of assuming that perhaps we were talking at cross-purposes. Really, try being less hostile and adversarial in the future.

      An external protocol is, quite obviously, one that is used to communicate with an external entity - i.e. on another box, running a different OS image, accessed via an external network interface.

      But this distinction does not exist in the software world; there are no "external" entities, merely interfaces to "other objects". These objects can be local or remote, they can be devices, etc. Yes, everything you point out is a "protocol", and yet, you called HTTP an "external" protocol. So what distinguishes an "external" protocol from an "internal" one? Are you drawing a distinction between a "native" protocol, such as a function calling convention, and one that must be "interpreted" and is thus "non-native"? Is this the distinction you're drawing between HTTP and the native, verifiable protocol in Sing#? It's a simple question.

      There is no reason why two objects on the same machine or even in the same address space cannot communicate via HTTP (and they commonly do for web services in the former case), so you're "external protocol" distinction does not make sense.

      It's selective in the sense of argument by selective observation. I realize you're not fluent in English, but please at least try to understand people before you disagree with them.

      Why would you assume I'm not fluent in English?

    19. Re:apples and oranges by cartman · · Score: 1
      There is no reason you cannot build this functionality on EROS...We have this functionality running on Linux right now with Java, mono, etc...why should the OS care how an IPC data string is structured?.. These are all guarantees you can have in any other OS... Other microkernels merely use the MMU to enforce isolation instead.
      The idea is that all applications running on the operating system (including their IPC) are either provably correct or bounded at run time.

      It's important that these restraints be enforced by the operating system. By enforcing these restraints in the operating system, you guarantee that things like buffer overruns and segfauls cannot occur. That's why IPC must be verified by the OS: it guarantees that an application couldn't possibly corrupt some other application. If these things were done using a VM in userspace (Java?) then the security and reliability holes would remain--as long as code verification is optional (by writing in Java rather than C), the malicious coder will opt not to use it.

      Also, the isolation enforced by code verification is much more stringent than the isolation enforced by an MMU. Virtual memory enforces isolation per process, whereas verification enforces isolation per buffer which is much more granular. Thus, not only are inter-process violations prevented, but buffer overruns are prevented as well. In addition, enforcing isolation through code verification does not impose the same run-time performance penalties as MMUs, which thus far have limited the adoption of microkernels.

    20. Re:apples and oranges by naasking · · Score: 1
      The idea is that all applications running on the operating system (including their IPC) are either provably correct or bounded at run time.

      1. This is simply impossible. The Halting Problem demonstrates that it's impossible to construct a general algorithm that can determine whether some other general algorithm will halt (unless this isn't what you meant by saying "applications running on the OS are [...] bounded at run time").
      2. It's impossible to prove that applications written in Sing#/Spec#C# are correct simply because the compiler cannot divine the intentions of the programmer, and thus it cannot know what the output "should be" in order to compare it to what actually came out. Only by combining languages and proof systems can we hope to achieve this end, and Sing#/C#/Spec# are still far from that goal.
      3. All IPC is necessarily bounded at run-time (limited by machine addressable limits), and in all microkernels the IPC data is validated to ensure that unauthorized accesses do not occur.

      Hmm... perhaps you should clarify what you meant here, since there are so many interpretations.

      It's important that these restraints be enforced by the operating system. By enforcing these restraints in the operating system, you guarantee that things like buffer overruns and segfauls cannot occur.

      This is a language-level issue, not an operating system one.

      That's why IPC must be verified by the OS: it guarantees that an application couldn't possibly corrupt some other application.

      IPC is always verified in every operating system. But IPC itself is not what causes buffer overflows or security breaches.

      If these things were done using a VM in userspace (Java?) then the security and reliability holes would remain--as long as code verification is optional (by writing in Java rather than C), the malicious coder will opt not to use it.

      I think the growing developer base for Java and .Net say otherwise. If verification exists, and it makes your programs more correct simply by turning it on, why wouldn't people use it?

      Also, the isolation enforced by code verification is much more stringent than the isolation enforced by an MMU.

      This is true. It remains to be seen whether it is practical however.

      Also, the isolation enforced by code verification is much more stringent than the isolation enforced by an MMU.

      Yes, but you are thinking of course-grained process-level operating systems like Linux. Operating systems built on microkernels offer much finer process granularity since their performance is so much higher. Files, directories, even sockets are all implemented as processes on EROS.

      In addition, enforcing isolation through code verification does not impose the same run-time performance penalties as MMUs, which thus far have limited the adoption of microkernels.

      True. Unfortunately, a compiler which can provide this sophisticated analysis is not here yet, or if it is, it clearly has some disadvantages in other areas (perhaps performance?).
    21. Re:apples and oranges by Salamander · · Score: 1
      every personal attack you make and every strawman you propose just makes you look more ignorant and childish.

      That's rich, coming from someone who has repeatedly been caught making false statements and won't even admit it. At least my responses have some actual content, even if I do let my annoyance show. I'd rather be rude than a liar.

      You are classifying "algorithmic" bugs as the superset of all types of bugs

      I am doing no such thing. You're the one who first referred to "algorithmic bugs" so why don't you define it? Until you do, I'll assume the intuitive meaning of bugs that represent high-level logic errors (e.g. deadlock/livelock, indefinite postponement, race conditions) as opposed to low-level implementation artifacts (e.g. incrementing the wrong variable, fencepost errors).

      Returning to my original example, a web server which incorrectly dispatches to a POST handler on a GET request has performed an invalid application state transition, even though the protocol state transition was valid. My original statement, stands: the verifier can do nothing about this sort of bug.

      Your statement stands as false, no matter how much you rely on argument by repetition. Dispatching to the wrong handler will often lead to generation of an invalid response, which can very much be caught by a verifier. This is less apparent in HTTP than in other protocols because HTTP was designed by an amateur, but it can still manifest in the form of invalid error codes or reply headers. In a better protocol it might be blazingly obvious in the form of a POST_REPLY to a GET request or GET_REPLY for a POST. Even if that weren't the case, the fact that there's one error a verifier could not detect in no way proves your claim that a verifier can do nothing. You still seem to be struggling with that distinction between "not every" and "none" don't you?

      But this distinction does not exist in the software world; there are no "external" entities, merely interfaces to "other objects".

      Yes, I'm sure a lazy app programmer who doesn't understand how protocols are implemented might think that. I'm not going to address that further because this distinction of protocols is a big red herring. It doesn't change whether your claim about verifiers not being able to do anything about protocol or "algorithmic" bugs is true or not.

      Why would you assume I'm not fluent in English?

      Because you have demonstrated repeatedly during this conversation that you have trouble not only with technical terminology but with basic language such as "not every" vs. "none" which would be quite obvious to most people. Granted, though, it might not be a language thing. There are other explanations.

      Not everyone who disagrees with you...is an idiot.

      There's that problem with "not every" again. No, not every person who disagrees with me is an idiot. That doesn't mean that none are, and the example that illustrates the distinction apparently thinks having the last word really matters. Go ahead. I'm done with you. You were wrong about Singularity not being a single-address-space OS, you were wrong that type and memory protection were the only guarantees, and you've been wrong on every secondary point since - even the irrelevant ones. You're obviously here just to argue, not to participate in any exchange of ideas.

      --
      Slashdot - News for Herds. Stuff that Splatters.
    22. Re:apples and oranges by naasking · · Score: 1

      That's rich, coming from someone who has repeatedly been caught making false statements and won't even admit it.

      I openly admit to anything I said that was false. Singularity is indeed a single-address space OS; I misread a section dealing with virtual memory and processes which led me to conclude it wasn't. That's a far cry from being a liar. But hey, you go on thinking the worst of people. Good luck with that.

      You corrected me on the single-address space issue, I left it at that. So because I didn't bow down and lick your boots and beg your forgiveness for being wrong on a particular point that I all of a sudden "won't admit to being wrong"? That's pretty childish.

      The only other point of contention were the capabilities of the verifier. We disagreed on the ability of the verifier to ensure correct "state transitions". It took you three exchanges to finally define what constitutes a "state transition", after which I agreed that the verifier could enforce "state transitions" over the external communication protocol. Unfortunately, that was not what I was originally concerned with, so here we are yet again.

      I am doing no such thing. (Re: defining "algorithmic" bugs as superset of all bugs)

      You just did in your parent post. I even quoted you. Really, your memory can't be that short.

      You're the one who first referred to "algorithmic bugs" so why don't you define it?

      I just did in the post you replied to. I even alluded to it, if somewhat imprecisely, in my original post.

      Until you do, I'll assume the intuitive meaning of bugs that represent high-level logic errors (e.g. deadlock/livelock, indefinite postponement, race conditions) as opposed to low-level implementation artifacts (e.g. incrementing the wrong variable, fencepost errors).

      In an abstract sense, an error is a state transition that the programmer did not intend in attempting to achieve his goals (either the algorithm itself was incorrect, or the algorithm was not implemented correctly). The class of errors I alluded to earlier, are those invalid state transitions which are internal to the core portion of an application (such as the HTTP request parser in a web server). The class of errors the verifier eliminates, are the state transitions associated with communicating with external entities. I'm not sure how you can possibly classify the two as synonymous, or one the subset of the other (as you did in your previous post). The two are quite clearly disjoint, and any intersection is coincidental (for those objects whose logic is merely communication itself -- such as a socket).

      Dispatching to the wrong handler will often lead to generation of an invalid response, which can very much be caught by a verifier.

      That's plain ridiculous. You are directly correlating internal state with external communication behaviour. There is sometimes strong correlation, but it is by no means guaranteed. If the correlation is strong, it is either due to the nature of the application (ie. a socket), or by coincidence. Coincidence is not a programming tool particularly for a reliable system.

      In the HTTP example, errors and success are both transmitted in an identical fashion. There is no distinction observable to the Singularity verifier. It is always texty request-texty response.

      This is less apparent in HTTP than in other protocols because HTTP was designed by an amateur,

      Ok, if you say so... Regardless, this problem is inherent to ALL texty or serialized protocols. SMTP, POP3, any byte-stream protocol really. The verifier cannot check any of these natively.

      Even if that weren't the case, the fact that there's one error a verifier could not detect in no way proves your claim that a verifier can do nothing. You still seem to be struggling with that distinction between "not every" and "none" don't you?

      Firstly, we are not discussing "a verifier", we are discussing the "Singularity verifier". I fully acknowledge that some future

    23. Re:apples and oranges by Salamander · · Score: 1
      Internal state transitions to an application are not verified, merely the externally visible communication transitions. Strong typing gets you closer to compiler verification of correctness. Dependent types would get you even closer. A built-in proof system could get you all the way there (if a bit tediously). The Singularity communication protocol verifier has the potential to also get you closer if the software component happens to be tightly coupled to a communication protocol.

      The software components in Singularity are tightly coupled to a communications protocol over a channel. That's the whole point. It's precisely those internal transitions that can be verified. It's the external (to Singularity) ones like HTTP that can't, but that hardly makes the verifier useless. You can say "not what I was originally concerned about" and "irrelevant to the issue at hand" and "not the class of bugs I was describing" but anyone reading this exchange can see you're lying. Those are exactly the things what you were concerned about, and your claims about them have all been wrong. No number of red herrings or whines about how you're being treated change that. You simply should have read and tried to understand the paper before you spouted off, and you didn't. Be smarter next time.

      --
      Slashdot - News for Herds. Stuff that Splatters.
    24. Re:apples and oranges by cartman · · Score: 1
      This is simply impossible. The Halting Problem demonstrates that it's impossible to construct a general algorithm that can determine whether some other general algorithm will halt...It's impossible to prove that applications written in Sing#/Spec#C# are correct simply because the compiler cannot divine the intentions of the programmer...
      When I said "provably correct or bounded at runtime" I didn't mean that the verifier could prove correctness according to human requirements. I meant that the verifier could prove a more limited kind of correctness: that buffer overruns, illegal casts, improper dereferences, and so on, cannot occur in a given program, regardless of its state. Obviously, it would be preferable to prove correctness in the broader sense, but that's impossible for another program to do. Still, that doesn't mean we should abandon the attempt to prove certain kinds of correctness automatically.
      All IPC is necessarily bounded at run-time (limited by machine addressable limits).
      Yes, but that kind of run-time bound is useless. We need to prevent a program from overwriting something in actual memory, like another program, the operating system, another region of memory, etc.
      If verification exists, and it makes your programs more correct simply by turning it on, why wouldn't people use it?
      Some people wouldn't use verification because they're malicious and write programs which are purposefully incorrect according to the verifier. For example, rootkits, trojans, worms, viruses, etc. Nobody writes those programs in Java. Instead, malicious programs are written in C (or other unsafe languages), but your computer, with its OS, will still gleefully execute those malicious programs written in the unsafe language. Wouldn't it be better if the operating system stopped the execution of a malicious program, regardless of where it came from or what language it was written in?

      Security constraints must be enforced by the operating system, not by languages or compilers! Otherwise, those constraints could be trivially bypassed by writing the malicious code in some other language (even assembly!) which your OS will happily execute anyway! Take Unix permissions as an example. Suppose they were enforced only by languages. Suppose they were enforced in the C standard library, for example, or suppose they were enforced at compile time using correctness checking. That wouldn't prevent a malicious cracker from modifying the output of that compiler (assembly language) to bypass those constraints.

    25. Re:apples and oranges by idlake · · Score: 1

      You're simply full of shit when it comes to operating systems, idlake. Stick to whatever it is that you know, which seems to be very little, and let the grownups do the real work

      And there you tell us in a nutshell why operating systems aren't going anywhere: the last half century of computer science and software engineering has passed you buy: you insult potential users of your software, you program in C, you don't do requirements gathering, you hand-craft your own object systems, and you think garbage collection is going to make your software slow. You're a dinosaur (and an ill-mannered one at that).

    26. Re:apples and oranges by benb · · Score: 1

      > These facilities make it impossible for any application to have
      > buffer overruns, segfaults, or overruns of other apps' data
      > -- as a result, all applications can run in ring 0 and virtual
      > memory is not required.

      Which is complete nonsense, because there are many other classes of security problems, some of them application-specific, other than buffer overruns and memory access.

      Or, tell me how Singularity helps me to protect cases where I want to right-click on an email address in the body of an email, but garantee (!) that there is no hole that would allow the sender to anyhow access my address book.

      > All that has nothing whatsoever to do with Eros.
      > The two projects are not even similar.

      Right. They are orthogonal. That's what he tried to say.

    27. Re:apples and oranges by benb · · Score: 1

      > If these things were done using a VM in userspace (Java?) then
      > the security and reliability holes would remain--as long as
      > code verification is optional (by writing in Java rather than
      > C), the malicious coder will opt not to use it.

      Wrong, because it's the normal coder and user that makes the choice, not the malicious coder. He is limited to exploit whatever is being used. If my mail server is implemented in Java, the attacker has to find a hole in that Java code or Java/VM itself to gain entry via the mail server. (And there is a mail server written in Java, BTW.)

    28. Re:apples and oranges by cartman · · Score: 1
      Wrong, because it's the normal coder and user that makes the choice, not the malicious coder. He is limited to exploit whatever is being used. If my mail server is implemented in Java, the attacker has to find a hole in that Java code or Java/VM itself to gain entry via the mail server. (And there is a mail server written in Java, BTW.)
      No, for several reasons.
      If my mail server is implemented in Java, the attacker has to find a hole in that Java code or Java/VM itself to gain entry via the mail server.
      But the malicious coder can gain entry through any service running on the system, not just the mail server. All services running on the machine must be written in verifiable bytecode to prevent intrusion.

      So perhaps the programmers writing daemons should use only Java, and perhaps users should run only Java services. That is half way to the solution.

      What about buggy or malicious drivers, protocl stacks, or loadable kernel modules? Users install those programs from CDs or from net downloads, and those programs run in ring 0 which means they can overwrite any memory on the system--they could even corrupt the JVM which previously had been secure. Is it really safe to have the operating system accept modifications to itself, without being able to verify that those modifications won't corrupt the rest of the operating system? Indeed, Microsoft claims that >85% of system crashes are caused by bad drivers written by 3rd party companies...

      No. To prevent intrusions, all programs running on the system must not have these problems, which means it must be enforced by the operating system.

  162. Jesus by Muhammar · · Score: 1

    I allways knew that going with MS was pretty hard choice - But until now I did not realize it was actually a choice between reliability - and performance. (I guess one cannot get everything - even with a great company like Microsoft.)

    --
    I doubt that we will ever figure out - and I suspect that even if we did figure out we couldn't do much about it
  163. Re:pseudo-academics should be careful what they ba by Anonymous+Writer · · Score: 1

    I don't think OSS is the holy grail which fixes everything, nor do I think MS is any better than OSS or worse for that matter.

    What do you think would be the best setup? I mean do you have any ideas on how things could be done, or have you seen any that just haven't reached the popularity of those two models?

  164. "This time we'll do it right!" by grikdog · · Score: 1

    Microsoft bashing is fun, especially when PR goons promulgate buzz instead of substance, as though everything that matters is virtual and buzz not only reshapes consensus reality in the realm of cash flow, but in the realm of actually getting things done. I roll my eyes too, but hey, you know, Microsoft has been getting things done for two decades. I'll cut 'em some slack with this one -- it's the same thing Steve Jobs did when he cut loose from legacy OS 9.

    --
    ``Tension, apprehension & dissension have begun!'' - Duffy Wyg&, in Alfred Bester's _The Demolished Man_
  165. Quoted text by Ahnteis · · Score: 1

    The main bits of the story
    Also, there is a link to this video
    http://channel9.msdn.com/ShowPost.aspx?PostID=6830 2

    ---

    "...it is impossible to predict how a singularity will affect objects in its causal future." - NCSA Cyberia Glossary
    What's New?!

    We recently released an extensive Technical Report describing the current state of the Singularity Project in great detail.
    Overview

    Singularity is a research project focused on the construction of dependable systems through innovation in the areas of systems, languages, and tools. We are building a research operating system prototype (called Singularity), extending programming languages, and developing new techniques and tools for specifying and verifying program behavior.

    Advances in languages, compilers, and tools open the possibility of significantly improving software. For example, Singularity uses type-safe languages and an abstract instruction set to enable what we call Software Isolated Processes (SIPs). SIPs provide the strong isolation guarantees of OS processes (isolated object space, separate GCs, separate runtimes) without the overhead of hardware-enforced protection domains. In the current Singularity prototype SIPs are extremely cheap; they run in ring 0 in the kernel's address space.

    Singularity uses these advances to build more reliable systems and applications. For example, because SIPs are so cheap to create and enforce, Singularity runs each program, device driver, or system extension in its own SIP. SIPs are not allowed to share memory or modify their own code. As a result, we can make strong reliability guarantees about the code running in a SIP. We can verify much broader properties about a SIP at compile or install time than can be done for code running in traditional OS processes. Boarder application of static verification is critical to predicting system behavior and providing users with strong guarantees about reliability.

  166. It's like this... by SuperKendall · · Score: 1

    See, it's like having a bunch of eggs. You want to keep them safe, right? So you build a really, really nice basket (or at least one that will hold all the eggs) and then plop those bad boys in there. Thus you are assured NOTHING can happen to those eggs, after all they are in one basket.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  167. IMPORTANT by MountainMan101 · · Score: 4, Informative

    I'm only replying to the parent so that this post is high up the screen.

    Look at page 31 of this PDF. Microsoft publish benchmark statistics showing Linux (and FreeBSD) to be better than Windows.

    ftp://ftp.research.microsoft.com/pub/tr/TR-2005-13 5.pdf

    1. Re:IMPORTANT by Anonymous Coward · · Score: 0

      Without breaking any copyrights,, can someone summarize the PDF page listed? I don't have FTP access outside the firewall at work and am interested.

      Thanks in advance

    2. Re:IMPORTANT by NetRAVEN5000 · · Score: 1
      "Microsoft publish benchmark statistics showing Linux (and FreeBSD) to be better than Windows."

      MS is monopolistic, not stupid. It's no secret that Windows blows - even many people who use Windows think it sucks.

      It's not all that shocking to me that MS is publishing the truth - when they published the lies, all it did was call a huge backlash from people who knew the truth. Now they're probably hoping to keep people from switching to Linux with a "we'll make it better. . . we promise!" kind of thing.

    3. Re:IMPORTANT by sstidman · · Score: 4, Interesting

      I'll admit that I don't know much about kernels, but I'll try to summarize. The chart compares performance between the new OS Singularity, FreeBSD 5.3, Redhat Fedora Core 4 (kernel version 2.6.11-1.1369_FC4), and Windows XP (SP2). The goal of the chart, stated in the paragraphs above, is to show that the new Singularity architecture does not suffer any performance hits in order to make a more secure system.

            The table shows the CPU cost of six different types of operations: "Read Cycle Counter", "ABI Call", "Thread yield", "2 thread wait-set ping pong", "2 message ping pong" and "Create and start process". For the first one, Windows seems to kick the butt of all others handily with Singularity being the worst of the bunch. For "ABI Call", each OS used different system calls that "operate on a readily available data structure in the respective kernels." The system calls seem to be completely different so I don't know if this test is valid, but the results show Singularity an order of magnitude more efficient than the others, with Linux beating Windows by a considerable margin and Windows beating FreeBSD by an equally considerable margin.

            For the "thread yield" tests, FreeBSD & Linux are equal, Windows beats them by a reasonable percentage and Singularity is more than twice as fast as the Unixes. For the "2 wait-set ping pong", which measures "the cost of switching between two threads in the same process through a synchronization object", the chart shows that Singularity is somewhat more efficient than Windows and Windows is more than twice as fast as the Unixes. For the "2 message ping pong", which shows the cost of sending a 1-byte message back and forth between two processes, Singularity is 4 times more efficient than Linux, which is somewhat better than Windows, which kicks FreeBSDs butt decisively.

            Lastly, for "Create and start process", Singularity is twice as fast as Linux, which is about 50% faster than FreeBSD. Windows comes out 7 times slower than Linux on this test. I don't know how much that matters in the real world since creating and starting a process is not something that is done hundreds of times a second.

            All that said, it should probably be pointed out that there are many ways to measure an OS. The M$ guys may have simply picked the ones that support their "see we don't suck" position. And given that Singularity is not a complete OS, I would expect that more overhead will be added later that will bring down these numbers. I guess we'll see.

      --
      Send/track messages to 100K people: www.xPressAlert.com
    4. Re:IMPORTANT by trewornan · · Score: 0

      You're spot on.

      Their FUD is becoming tired so they've switched to the vapourware tactic.

      It's bollocks - if they make a system that's secure, stable, etc then it'll break all the Windows Apps that are out there. Then if you've got to go through a major migration anyway most rational people would consider what options were available. It changes the question "Which is cheaper, upgrade windows or migrate to linux" to "Which is cheaper migrate to Singularity or migrate to linux". Microsoft lose all the advantage their illegal monopolistic practices give them.

      The more I hear from Microsoft the more desperate they seem lately.

    5. Re:IMPORTANT by gklnx · · Score: 0

      If it does not have Quake FPS its no good benchmark

    6. Re:IMPORTANT by rtb61 · · Score: 0

      Or are they just re-iventing yet again the windows nt marketing line versus the window marketing 98 line. Perhaps if microsoft marketing research were doing a few less lines themselves they could come up with something original.

      --
      Chaos - everything, everywhere, everywhen
    7. Re:IMPORTANT by NetRAVEN5000 · · Score: 1

      Have you ever seen that picture of the original MS staff way back in the '80s or whatever? They look like they probably did do lines, or smoke weed or something.

  168. I heard of this by Anonymous+Writer · · Score: 2, Funny

    Isn't it used in Romulan Warbirds?

  169. How can they build an OS in this day and age? by Lester67 · · Score: 1

    It seems as if every method of handling all the major subsystems of an OS has been patented by someone and/or his brother.

    Honestly, this thing has patent lawsuit written all over it, and no one outside Microsoft has even seen a lick of code yet.

  170. Beowulf Cluster by Anonymous Coward · · Score: 0

    Imagine how slow a Beowulf cluster of these would be!

  171. MSR is sort of like Bell Labs in several important by einhverfr · · Score: 1

    ways....

    Bell Labs and MSR are both highly accademic institutions which have supported research not immediately profit-oriented to the parent company. And the parent company has generally failed to do a whole lot with them.

    Heck, Bell Labs invented cell phone technology in the 1930's but for a number of reasons (concerns about reliability, lack of emphasis on miniaturization, etc) they never rolled it out until after the breakup of 1984. Again, electronic switching systems were developed long before they were rolled out and this hurt AT&T when MCI and competitors were able to roll out AT&T's inventions far faster than they did.

    Also, how many MSR projects have ever made it into a Microsoft product?

    I have a lot of respect for MSR. But this doesn't translate into respect for Microsoft Corp.

    --

    LedgerSMB: Open source Accounting/ERP
  172. I think the point is somewhat murky, myself by jd · · Score: 2, Insightful
    The first implementation is indeed innovative. I'd call Gopher and WAIS truly innovative as information delivery systems and the web as innovative as a presentation system. For plain information, Gopher and WAIS are still technically superior.


    I would argue, however, that later generations can be innovative - provided they do something revolutionary in and of itself. For example, CERN's webserver was the first (and therefore innovative by being first) but I'd consider NCSA's webserver to to have posessed qualities that the CERN server did not have, in a manner such that NCSA's webserver (IMHO) deserves the title of innovative as well. Although Apache has yet more qualities, I would not consider those to be in a manner that justifies such a title.


    By implication, I'm saying that a quality must have some attribute that distinguishes itself above and beyond being a mere addition, for the idea/project to be called a true innovation. To me, that attribute is that the addition not simply be an extrapolation or an interpolation of what already existed but must exist outside of the covered space, yet intersect the covered space in such a manner that the extension is a natural extension, not forced.


    The "dumb person's test" for true innovation is that it must be so difficult to see in advance that it had truly occured to nobody at all. EVER. Yet be so obvious once found/developed that nobody really realizes it hasn't always been there,

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:I think the point is somewhat murky, myself by MikeFM · · Score: 1

      My experience is that most innovations aren't new - it's just that when enough people become aware of the idea that they realize it exists that whomever has the best known implementation of that idea is called innovative. Which is why most inventions happen in more than one place, by more than one person, at the same time. Lightbulbs were around for a long time before Edison's lightbulb took off but he still gets the credit for inventing the lightbulb. Ideas very much like the web were around for a long time before the web but that's just the first version to have the needed features and be in the right place at the right time in order to take off.

      True innovation doesn't really exist. We're all taking ideas from each other and adding our own observations and ideas with those all the time. Invention isn't sitting down and farting out something totally new. It's making tiny incremental changes that suddenly add up to something significantly different to be classified as something new.

      Microsoft's problem is that they have R&D that might be innovative but they rarely, if ever, use those innovations in real products in a timely manner. Also MS seems blind to the rest of the world so they innovate things that others have already done - sometimes decades after others have done it. Sort of a problem. If they innovate ideas when others are innovating the same things at the same time then they can still get by with claiming to be innovative but if they are a year or a decade behind others then it doesn't really count anymore.

      --
      At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
  173. Hmm. As Expected. by TwoTailedFox · · Score: 1

    I get an Error when using Firefox.

    On topic, I'm wondering how well an OS written in C# would do, if released.

    --
    ~The TwoTailedFox posts again....
  174. is this a prime example of what MS has to offer us by Anonymous Coward · · Score: 0

    went to the site http://research.microsoft.com/error.aspx?aspxerror path=/os/singularity/default.aspx as mentioned in the story & was greeted with an aspx server error... the irony is just too great!

  175. EROS was not "new" by Jim+McCoy · · Score: 1

    EROS was a direct descendant of KeyKOS, a capability-secure OS that ran on IBM S/370 systems, and Coyotos is a direct descendant of EROS. FWIW, KeyKOS was itself based upon a prototype design for a secure mainframe OS called GNOSIS (which I do not think was ever actually implemented, while KeyKOS was a real product back in the days when mainframes ruled the earth.)

    Care to try again?

    1. Re:EROS was not "new" by jcr · · Score: 1

      EROS didn't have any KeyKOS code in it. It was indeed written from scratch.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    2. Re:EROS was not "new" by Curt+Cox · · Score: 1

      MINIX?

  176. Finally by pacanukeha · · Score: 1

    They are going to use Java OS.

  177. Re:Looks interesting, could lead to a better found by Dominic+Burns · · Score: 1

    "Judge technology by it's merits and pitfalls not by it's creators past acheivement, or personal disputes with it's creator."

    Can you say 'vendor lock-in'? Microsoft is driven by money - that's it. Like it...or don't. But don't expect people to blindly trust something that's so utterly ubiquitous and, indeed, open to abuse...because you're asking too much.

    What happens when 'they' crack the human machine interface? Will MS own a bit of my brain? My kids' brains? Their kids' brains?

    Oh, the humanity!

  178. Cory Doctorow by hardwarejunkie9 · · Score: 0

    Something tells me the great force behind BoingBoing.net, Cory Doctorow wasn't envisioning THIS when he wrote about the Singularity....

    --
    I like losing arguments, it just means that I can take your point and make it my own.
  179. Everybody does it (Re:MS has .. OS from Scratch!) by rhyre417 · · Score: 1
    Hey, at least they're going to the right conference and presenting papers! Every large research group (and/or person with a lot of time on their hands) eventually builds their own operating system, or creates their own programming language.

    Choices was an OS written in C++

    I believe DEC WRL wrote operating systems in Modula-3 (type-safety helped here)

    The Mayflower project (at MIT and elsewhere) planned to use CLU (a type-safe language from MIT) as a base.

    The C# guys are adding dynamic language features to their VM, so Microsoft research can hire/distract/annoy a lot of Lisp and smalltalk fans.
    It's all good!

  180. Yawn by Salamander · · Score: 5, Informative

    I already wrote about this four days ago so I won't repeat the whole thing here. Short version:

    • Microkernel design, single-address-space implementation: good
    • Extensive compile-time checking of code that eventually runs native (not interpreted/JIT): good
    • Checking protocol behavior as well as lower-level function contracts: great
    • No deadlock/livelock checking: ok for now (it's a hard problem)
    • No checking of responses to component failure: oops
    • Not even a mention of making it distributed: weird

    Even shorter version: lots of great ideas, lots of work still to be done. Anybody with a clue about operating systems should be following this with interest.

    --
    Slashdot - News for Herds. Stuff that Splatters.
  181. Borrowers of ideas by ThomasCR · · Score: 1

    This is, what MS always was. The takeover of an idea, a name, a shape ... is their great art, since the beginning. And I am not a blind MS hater at all!

  182. dreaming of a new OS... by Anonymous Coward · · Score: 0

    My dream for a new OS...

    Start off with 1 widget set, and a single UI design. Make it HARD for programmers to deviate from the UI design. I didn't say make it easy to follow the basic design (that should be a given), but make it really hard to

    Then design in the basic functionality, and then build your main programs - network, text, graphics, video, sound, browser and database, all with a standard, well written API/ABI. The main programs would be skinable and plugable. For example, text would be skinable as the composer for email, a notepad/vim/text editer, a full blown word processor, etc. Plugins would allow for additional features not supported by the origional program, for example, new file formats, email, game functions, etc.

    I want the system to be stable as can be. I want a multi-user system, with a sane networking design. I want to be able to access files and programs on other systems easily. I want

    I want it to be easy to support. I don't really care if I use the same kernal on my toaster or not, I want a product that is truely engeneered to work, and to work well. I guess I want the best from DEC, NeXT and BeOS, all rolled into one package.

    That's my dream for a new OS. I wonder who will be the first to deliver it?

  183. Check into reality sometime. by khasim · · Score: 1
    Since you are pointing out the modifications to the posts and comparing the "alleged" disparity in comment, you sir, ARE karma whoring.
    Strange ... how can being mod'ed down be considered "karma whoring"?

    It would seem, based upon the current ratings (mine shown):
    0, Troll
    1, Offtopic
    1, Troll
    0, Troll
    2, Redundant
    that questioning Microsoft leads to lowered scores. While claiming that /. is anti-Microsoft leads to raised scores.

    Or are you defining "karma whoring" the same way you define "innovation"?
    1. Re:Check into reality sometime. by devilsadvoc8 · · Score: 1

      The point is that since you care not about content and prefered to argue mod points in the parent post you are looking for karma not intellectual discussion.

      --
      B O R I N G
  184. So... by ohstoopid1 · · Score: 1

    Anyone have screenshots?

  185. Unsurprisingly by Null+Perception · · Score: 1

    When the first version was compliled, the infinitely dense singularity manifested itself as the one we call Steve Ballmer.

    --
    Great new book on Evolution: The Greatest Show on Earth by Richard Dawkins
  186. Dependability instead of performance... by JustNiz · · Score: 1

    *Laugh*
    Since when did any Microsoft OS have good performance?

  187. Dependability vs. Performance by BigLinuxGuy · · Score: 1

    While I applaud the effort to create a dependable operating system , dead-slow dependability is an academic exercise at best. However, we should keep in mind that this is an R&D project and therefore by definition is an academic exercise from which some practical lessons/applications may arise.

    I will note that I have never had a client ask me to make an application perform more slowly though....

  188. No No No by Anonymous Coward · · Score: 0

    That would be a big bang singularity...

  189. Encouraging by petrus4 · · Score: 1

    I've believed for a while that Microsoft need to get away from their current codebase/s, and it's gratifying to discover that apparently at least a few people within the company feel the same way. They need to get this out the door ASAP, but if they can pull it off, this could be the rebirth opportunity they have so desperately needed.

    The problem though is that even if the core is good, as some have suggested here before, they may not be able to resist the temptation to slather security-reducing crap all over it in the name of user-friendliness. We shall see.

  190. Hmmm... by jav1231 · · Score: 1

    No screenshots...this must be the OS designed to run DukeNukemForever!

  191. Even the name shows the uninspiration of Microsoft by daveinla · · Score: 1

    Has anyone noticed that even the Singularity name is an analogy with the Unix (unique) name ?
    They didn't make that to obvious so that people don't have to much high hopes on them !

  192. Re:Nope. by An+ominous+Cow+art · · Score: 1

    Wierd Al rules!

    I agree with you about the reasons for despising Microsoft. I had no particular feeling for or against them at first. I learned contempt through using their products and watching their corporate behavior over the last 16 years or so...

  193. Re:Looks interesting, could lead to a better found by Shotgun · · Score: 1

    looks promising
    technologies that have to this point only been theorized
    disgusted with general microsoft bashing
    Judge technology by it's merits and pitfalls not by it's creators past acheivement

    You can't judge a technology, only an implementation. Implementations from a vendor tend to follow the same quality trends. So a company known for slipshod and insecure implementations is experimenting with some unproven technologies, and you call that 'promising'?

    Can I have a toke of that stuff your smoking?

    --
    Aah, change is good. -- Rafiki
    Yeah, but it ain't easy. -- Simba
  194. MS didnt name it. by Anonymous Coward · · Score: 0

    MS Research did. Learn what MS Research is and realize you are putting down respected developers, researchers, scientists.

    Of course i don't expect /. idiots to know this stuff.

  195. Lisp by fionbio · · Score: 1

    As an experienced .NET programmer with some Common Lisp knowledge, I'd say that it will take C# another ten years before it reaches the level of CL. Well, at that point it will probably become just another Lisp dialect, differing from CL as much as modern .NET differs from Java. Then it will take them another ten years to match Genera development environment capabilities.

  196. Unics vs. Singularity ? by dzafez · · Score: 1

    Don't you see this?

    Both names are based upon the number 1.

    Hell, I forgot, what this is supposed to mean, sorry, I'l post again, when sober ...

  197. Damn MS trickery! Don't buy into it! by NetRAVEN5000 · · Score: 1
    "operating system under development" . . . "designed new from the ground up, built on a new language and designed with emphasis on dependability instead of performance."

    Dammit MS! It's amazing that anyone will buy your products anymore.

    "Designed new from the ground up", "Designed with emphasis on dependability instead of performance" - didn't they say that's what they did for Vista? Didn't they promise that it'd be rebuilt from the ground up with security and stability in mind?

  198. Re:MSR is sort of like Bell Labs in several import by sickofthisshit · · Score: 1

    Can you be a little more specific about what you mean by "cell phone" technology out of Bell Labs?

    I know they were working on RF/microwave technology, for *stationary* microwave relays, but to me "cell phone" = "wireless phone sets, being handed between multiple base stations without dropping calls"

    I don't think Bell Labs was working on that in the 1930s.

  199. Heres one: by 0kComputer · · Score: 5, Insightful

    How about IXMLHTTPRequest, or what everyone now so fondly calls AJAX now that its all the rave.

    --
    Top 10 Reasons To Procrastinate
    10.
    1. Re:Heres one: by Anonymous Coward · · Score: 0

      IXMLHTTPRequest takes the idea of a frame with a document inside parsed using DOM.

      Sure IXMLHTTPRequest gets rid of the frame and gives us a bit better API... It's a nice extension to the API, but it's more a natural evolution then some fantastical new innovation.

  200. Is this not like containers in Solaris 10? by lenehey · · Score: 1

    This sounds a lot like containers in Solaris 10.

  201. How about a truly good PL instead of a new O/S? by master_p · · Score: 1

    Since there exists truly enormous amounts of code written, I think there is no justification from building a new O/S from scratch.

    A new truly good PL that minimizes coding but at the same time provides a way to express all the requirements of an application so as that the compiler verifies them at compile time is truly needed.

    Functional programming languages have been quite a step in the direction towards program correctness, but they have performance problems. We need new calculi for imperative languages that manage referential transparency as specification, rather than an ad hoc principle over which a programming language is built.

  202. YOW! by glassgnost · · Score: 1

    with no prior agreement as to the size of an angel...

    ...or who's cranium represents the pin.

  203. Just Great by JimXugle · · Score: 1

    So now we'll be hindered by virtual speed limit signs instead of Crashes, corruptions, etc?

        _____________
      | |
      | SPEED LIMIT |
      | ___ |
      | | |
      | --| |
      | ___| |
      | ___ __ |
      | | _ |_| / |
      | |__| | | /_ |
      |_____________|

    --
    -jX

    Don't you just love politics? It's like a comedy of errors.
  204. WOW!!! by rastin · · Score: 1

    All the things you've come to expect from Unix, without the platform portability!

  205. True, total innovation by jd · · Score: 1
    I believe it to be possible for something to be truly, totally original - for an idea or artifact to have no precursors in part or in whole. If that were to be the definition of innovative, then there would have been perhaps a dozen true innovations in the entire history of humanity. I also believe that - because such work is so rare - that such innovations should be prized above anything else on Earth. There is absolutely nothing in the Universe rarer than creative talent at this level of purity.


    If you're willing to relax the rules a little - require no obvious precursors - then the number of innovations grows considerably. But they're still pretty thin on the ground. I'd say that there would be maybe one or two such innovations every decade, somewhere on the planet.


    If you go further in relaxing the definition, and merely require no trivial precursors (ie: it cannot be a simple extrapolation or interpolation of what already exists), then there are maybe half a dozen each year.


    I tend to go somewhere between those last two cases, in the way I look at innovation. I want the term to be used often enough to be meaningful to people, without being so broad as to be meaningless within itself.


    However, I would like a clear term that is expressly for the rare cases that meet the first definition. A spectrum isn't just defined in terms of the progression along it, it is also defined in terms of the extreme ends. Calling them "totally unoriginal" and "totally original" tells you nothing other than they're points on the originality continuum. Zero and infinity, on the number line, are not just points. The expression of zero unleashed whole areas of mathematics, as did the expression of infinity. Their value in defining the limits vastly exceeded the value of any other point on the number line.


    What this argument over innovation does is tell us about the line of creativity. It does not define the limits and we're all still arguing over the relative merits over some small segment of the line in its entirity. I think it's time to study the line, the dynamics of it, the maths of it, and the limits of it. Do that and we won't just agree on what is innovative, we'll be able to express the innovation in a way that has meaning.

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
  206. Partial Summary and Comment by RedLaggedTeut · · Score: 3, Informative

    Results are mixed;

    According to the benchmarks published there

      - at most OS jobs like threading/process creation, Singularity is at least twice as fast as linux, Linux is very fast at process creation, while XP is good at threads

      - in File Operations FreeBSD and Linux beat XP and Singularity at random reads

      - in File Operations XP beats Linux and Singularity at sequential reads, with the exception of FreeBSD being fastest if blocksize is high(and very bad for small blocksize)

      - linux executable size are larger than these of the other OSes, (whatever that means, more good coding, or less bad code SCNR)

    Please bear in mind that a benchmark does not it tell whether the "slower" OS actually invested more time in doing some smart stuff that pays off in some other way.

    --
    I'm still trying to figure out what people mean by 'social skills' here.
    1. Re:Partial Summary and Comment by barryman_5000 · · Score: 1

      Linux executable size is larger due to visibility issues with a pre 4.0 gcc. It keeps certain symbols from being removed that should be. I still wouldn't doubt that windows would have a smaller executable though.

    2. Re:Partial Summary and Comment by Wikipedia · · Score: 0

      I guess Be, Inc. were right all along.

      --
      P2P Anonymous Distributed Web Search: http://www.yacy.net/
  207. Re:Nope. by Fareq · · Score: 1

    making novel uses of existing technology is "innovation"

    creating new technology is "invention"

    Sometimes people use "innovation" to mean creating new technology. I don't know whether this is an acceptable use of the word or not, but either way, taking existing technology and applying it in a new way is most definitely innovative.

  208. Holy Priority Shift, Batman! by VampWillow · · Score: 1

    "designed with emphasis on dependability instead of performance."

    Does this mean Singularity will be as dependable as current Windows OSes are performant?

    Shriek!

  209. SIP? by k-sound · · Score: 1

    Being somewhat involved in the VoIP(/telecom) world I think Software Isolated Processes is a poor name for their new technology. SIP as in Session Initiation Protocol is the de facto standard for VoIP communication, hell even Microsoft has adopted it

  210. I Know, I Know ! by da5idnetlimit.com · · Score: 1

    /almost serious

    They gonna take BSD, and code a new UI on it, and they'll call it Ultimate Microsoft Windows.

    A la Mac OS X... /almost...

    Now I'll just step back and look at my karma burning.
    But you know I may be right, and for the Mac part, you know I am ..8p

    --
    It takes 40+ muscles to frown, but only four to extend your arm and bitchslap the motherfucker
  211. Singularity: there is no escape! by sinewalker · · Score: 1

    Quick: how fast can we start running, before the Singularity is built an we simply cannot ever escape from Microsoft? That must be the evil plan...

    --
    “Our opponent is an alien starship packed with nuclear bombs. We have a protractor.” — Neal Stepnenso
  212. You're just swapping one term for another. by khasim · · Score: 1
    making novel uses of existing technology is "innovation"
    So, now the question is "how do you define 'novel' in that context"?

    In other words, we're back at the beginning.
    I don't know whether this is an acceptable use of the word or not, but either way, taking existing technology and applying it in a new way is most definitely innovative.
    And we're still back at the beginning.

    What is the "new way" that you claim is "novel", therefore, "innovative"?

    The "wheel" was an invention.

    Using the wheel to create a cart for humans to push or pull was innovative.

    Domesticating horses/mules/oxen was innovative.

    Adding a horse/mule/ox to the cart was innovative because it replaced the human and required some expertise in animal control. It also required the invention of the "harness" and/or "horse collar".

    And so on.
  213. File manager: Schroedenger's Explorer by Anonymous Coward · · Score: 0

    ...it might suck, it might not.

    Tell me this, are *YOU* going to be the first to open the box?

  214. Hmmm... by eclectic4 · · Score: 1

    "...with emphasis on dependability instead of performance.""
    So, they're making a Mac... again?

    --

    "The greatest obstacle to discovery is not ignorance - it is the illusion of knowledge." - Daniel Boorstin
  215. architecture-independent drivers by Mihai+Cartoaje · · Score: 1

    I have had an idea like this. My idea was for drivers to be written in a language in which the result of programs is independent of instruction set architecture and compiler, like the description here .

    The drivers would be distributed as binary code for a virtual machine. This would allow a company to ship one version of the driver for their device, which would work on all architectures, like, x86, PowerPC, Alpha, Itanium, etc.

  216. Re:Nope. by koreaman · · Score: 1

    You could back up your whole hard drive on a floppy diskette.
    You're the biggest joke of the internet.

  217. Dependability over performance! by Ingolfke · · Score: 1

    designed with emphasis on dependability instead of performance

    And Intel and AMD simultaneously wet themselves.

  218. Metaphor, metaphor, Slashdot inspired. . . by Fantastic+Lad · · Score: 1
    I enjoy it when the editors (deliberately?) put two stories on the same page which suggest a common thought pattern.

    With IBM slowing the speed of light with their latest generation of chip technology, and with Microsoft working to engineer a singularity. . . Knowledge is Light, and black holes suck up light as surely as computer-powered DRM and RFID and similar technologies work to track and control and limit. Slowing Light, indeed!

    As this reality of ours is little more than a shared holographic dream sequence, (there is no such thing as matter; those atoms divide all the way down to squiggles of energy, and what is energy other than a medium for consciousness to exist within and self-observe?), it is my editorial opinion that metaphor flies thick through this world of ours, and those who pay attention are more able to surf the bumps and rough spots on the ride of Life.


    -FL

  219. Slashdotting... A data gathering opportunity. by X-rated+Ouroboros · · Score: 1

    Has anyone bothered to collect the data about /.ing in regards to how long it taks for a server to fall over and burst in to flames to see what role OS plays?

    Load testing to the point of failure in real world conditions is a daily occurance for sites listed on /.. What's being done with all the load data? It's mentioned every few "Dang, dead before the First Post!"about how /. should offer to host the content of some of the smaller sites rather than just hammering them into the ground without notice... Why not offer to do that not so much out of benevolent concern, but to have a reliable source of real-world stress that can be applied to a server whose configuration can be modified under controlled conditions?

    Compare products from different vendors, multiple products from a single vendor, several configurations of a single product... all in a controlled and replicable real-world load condition.

    Who needs benchmarks?

    --
    Simple Machines in Higher Dimensions
  220. OpenVMS by Anonymous Coward · · Score: 0

    dude, wasn't this once called OpenVMS? :)

  221. The Slashdot profit plan by MooUK · · Score: 1

    1. Make a reasonably, but not overwhelmingly, funny comment.
    2. Note that you expect to be modded down.
    3. ???
    4. +5 Funny!

    Honestly, it works every time.

  222. Reminds me, perhaps incorrectly, of the Brix OS by Anonymous Coward · · Score: 0
  223. slow enough by ZhuLien · · Score: 1

    Windows is slow enough (from a responsiveness point of view).

  224. Totaly useless by Anonymous Coward · · Score: 0

    Dependability is quite useless if my games cannot run at > 60fps!

  225. The new OS, developed in C# . . . by Ph33r+th3+g(O)at · · Score: 1

    . . . will require downloading the .NET runtime.

    --
    I too have felt the cold finger of injustice.
  226. Re:pseudo-academics should be careful what they ba by drsmithy · · Score: 1
    I won't trust the security of a M$ OS until the source is opened. (Note I don't mean open source, just that the source is available to all for peer review, even if full copy and distrobution rights are maintained).

    Considering how few security breaches have anything to do with coding problems, I think that's a pretty ridiculous measure.

  227. i can allready see the packaging by indy_Muad'Dib · · Score: 1
  228. Re:pseudo-academics should be careful what they ba by gumpish · · Score: 1

    Considering how few security breaches have anything to do with coding problems, I think that's a pretty ridiculous measure.

    So security breaches are mostly the result of... ? Social engineering?

  229. Get a clue. by khasim · · Score: 1
    The point is that since you care not about content and prefered to argue mod points in the parent post you are looking for karma not intellectual discussion.
    Yet my posts have been mod'ed down.

    My statements have offended the moderators.

    I have made statements that CONTRADICT the bias of the moderators on /.

    "Karma whoring" means when one makes statements that the moderators will mod UP. Not DOWN.

    If you are capable of reading, you will see that many of those posts have been mod'ed "Troll".

    "Trolling" is the OPPOSITE of "karma whoring".

    I trust that this revelation will not cause you undue mental anguish.

    Today, I posted comments to the effect that Microsoft was not innovative and those comments were ruled as "trolls" by the moderators.

    On /. today, "bashing Microsoft" as you put it is not "karma whoring".

    Either way, you are wrong. Live with it.
  230. Stop playing god by smartdreamer · · Score: 1
    There was IBM Slows the Speed of Light, now MS creates singularity (black hole?). What's next? Pixar's pulsar?

    Let us stop companies playing physicists.

  231. No - that's the save dialog by Anonymous Coward · · Score: 0

    N/T

  232. switching between two threads by Mihai+Cartoaje · · Score: 1

    In linux, "switching between two threads in the same process through a synchronization object" can be done by the first thread doing a system call to increase a semaphore to activate the second thread, and then the first thread doing a system call to lower a semaphore to put itself to sleep.

    I suppose Ms-Windows has a way of doing this with only one system call, which might explain the factor of 2 in the parent post.

  233. Apache spawns one process per connection by Divebus · · Score: 1
    "I don't know how much that matters in the real world since creating and starting a process is not something that is done hundreds of times a second."

    Apache. Every connection spawns a unique process which terminates upon completion. That's one of the things that makes it a little more secure - you can perhaps exploit the process, but before you kno

    --

    Most of the stuff on /. won't survive first contact with facts.
    1. Re:Apache spawns one process per connection by zootm · · Score: 1

      Interestingly, I believe that that's exactly the kind of infrastructure that this system is trying to enforce.

  234. Dependability Instead of Performance. by Deliveranc3 · · Score: 1

    Sorry What?

  235. APRIL FOOLS! by SilverwoodUG · · Score: 1

    Microsoft with emphasis on dependability instead of performance

    is it april fools day already?

  236. diff vs Plan9/Inferno, TAO/Intent, AS400? by AReilly · · Score: 1

    I haven't read the whitepaper yet, but the front page article makes it sound a lot like any of the OSes listed above. What's new here? Not to mention any of the proposed (but not deployed?) Java OS systems...

    --
    -- Andrew
  237. An old but good quote here... by andrewski · · Score: 0

    "Those who don't understand unix are condemned to reinvent it, poorly."

    In this case you can replace 'unix' with 'Mach' and apply it to Singularity. Except, of course, you have to use Microsoft's wacky C# dialect.

  238. Re:Features? New OS? not really... by kiwipeso · · Score: 1

    Most of these new features are not new ideas, seeing as I have had most of them 5 years ago. It is only now that the technology has advanced enough to let me do this right for KAOS.
    What I would say is that this would take a fair while to complete, as I have taken about 4 years to think of 90% of the features I want in my operating system.
    However, I am using proven technology that has merely been abandoned, and I intend to rescue what I can.

    --
    - Kaos games and encryption systems developer
  239. Why develop one internally? by The+OPTiCIAN · · Score: 1

    They could just buy Palm, and get the (proven) Be codebase. No legacy issues, reasonable documentation, kernel in C, C++ API, potential to hire back to it some of the best OS engineers around.

    It's just waiting for someone to come along, fix up the quirks and expose the APIs for .net. Some loss of face, but a lot of people would have respected them for it as well :) And they could knock palm out of their PDA market at the same time.

    --


    Believe with me, my saplings.
  240. Re:pseudo-academics should be careful what they ba by Anonymous Coward · · Score: 0

    Um, it *is* open for peer review just as you asked.

    It's not open generally, but literally thousands of people outside Microsoft from governments to academics to major customers have NDA'd access to the source code of (for example) Windows. No, not any Tom Dick or Harriet can see it (and probably not you).

    IAAME (MS employee) and writing code, we are well aware it may be viewed by people outside the b0rg cube. *Especially* security sensitive code.

  241. New Overlords Welcoming time? by kalirion · · Score: 1

    I wonder if this is what they're trying to develop.

    1. Re:New Overlords Welcoming time? by mozkill · · Score: 1

      well, if they are trying to develop a black hole from which nobody can escape, they have already done it!

      --

      -- Betting on the survival of the media industry is a serious risk. I advise investing elsewhere.
  242. Re:pseudo-academics should be careful what they ba by drsmithy · · Score: 1
    So security breaches are mostly the result of... ? Social engineering?

    Users. This encompasses user error, user ignorance, social engineering, malicious sabotage, poorly configured machines (admins are "users", too) - anything where the user must play an active part to the breach (so, just about every email "virus", all those bits of spyware that get installed when the user clicks "OK", etc).

    *Very* few security breaches happen because of coding problems (buffer overflows, backdoors, bugs, etc).

  243. Re:MSR is sort of like Bell Labs in several import by einhverfr · · Score: 1

    Actually, they were working on a basic FDMA wireless mobile phone system for a long time. The first trials of such a system started in 1946, so I am inclined to think that Bell Labs had the basic concepts down at least 10 years earlier at the latest.

    Interestingly I was wrong on one important point. Advanced Mobile Phone Service was an AT&T subsidiary which began to roll out cell phone service in 1982 and was split up among the baby bells when the divestiture occurred.

    --

    LedgerSMB: Open source Accounting/ERP
  244. Read the posts carefully by cartman · · Score: 1

    > > These facilities make it impossible for any application to have
    > > buffer overruns, segfaults, or overruns of other apps' data
    > > -- as a result, all applications can run in ring 0 and virtual
    > > memory is not required.
    >
    > Which is complete nonsense, because there are many other classes of
    > security problems, some of them application-specific, other than buffer
    > overruns and memory access.

    The original paragraph did not claim that bytecode verification would prevent all security problems. Rather, it specifically claimed that verification would prevent "buffer overruns, segfaults, overruns of other apps' data". (See above).

    > Or, tell me how Singularity helps me to protect cases where I want to
    > right-click on an email address in the body of an email, but garantee(!)
    > that there is no hole that would allow the sender to anyhow access my
    > address book.

    The original paragraph did not claim that Singularity would prevent you from right-clicking something, or would prevent an app from sending out your address book. It claimed that bytecode verification could prevent buffer overruns, segfaults, overwriting of other apps' data, etc...

    > Right. They are orthogonal. That's what he tried to say.

    No, that's not what he tried to say. The parent post said: "They [Singularity] aren't the first... Check out EROS [eros-os.org] for an implementation that exists now" which clearly (and wrongly) implied that EROS was an implementation of the same idea, which came before. And the subsequent post claimed "Singularity is a Microkernel, EROS is a Microkernel" which is clearly intended to point out the supposed similarity.