Slashdot Mirror


Bob Metcalfe on Open Source, IPv6, IETF

prostoalex writes "The inventor of Ethernet Bob Metcalfe is interviewed by AlwaysOn on current issues. Metcalfe is known for challenging commonly accepted wisdom and this time he's quite confrontational. On open source and operating systems: "If you look at Windows and Linux, both are based on 25-year-old technology. Windows is sort of a GUI version of the Mac's operating system, and Linux is of course Unix, which stems from 1968. These are both old clunkers. So the question is, Where are the new operating systems likely to come from?" On IPv6 adoption and IETF: "Back when you attended the IETF, you all looked down your noses at the ITU (or I guess it was called CCITT at the time)--the entrenched, corporately manipulated, corrupt, competent standards being embodied in IT. We were the IETF--the swashbuckling, institution-oriented, open people, the rebels. That's changed now. The Internet has arrived, and all of those people are now just like ITU: IETF has become the ITU.""

70 of 438 comments (clear)

  1. Inconsistent Rant by XorNand · · Score: 5, Insightful
    If you look at Windows and Linux, both are based on 25-year-old technology. Windows is sort of a GUI version of the Mac's operating system, and Linux is of course Unix, which stems from 1968. These are both old clunkers. So the question is, Where are the new operating systems likely to come from?
    I guess someone should tell automakers that they should reinvent a mode of transportation from scratch. That four wheels, an engine, and brake and throttle thing is so passé nowadays. Plumbers are going to be pretty upset to learn that using pipes to carry water is so several-centuries ago.

    There's no doubt that Mr. Metcalfe is quite bright and has contibuted greatly to the IT world, but I don't understand this rant. If he doesn't see the innovation, I guess he's never compared Slackware '96 to today's distros, or Windows 3.1 to WinXP. Apple certainly can't be ignored here either. Where are the new operating systems likely to come from? I'm going to take a wild guess, and say "probably from the OS's of today." They don't need to be completely rewritten every few years to count as progress. Even the emergence of UNIX itself was evolutionary, not revolutionary.

    It's also interesting that he clearly shows a lack of faith in the OSS community, but then digs at the IETF for evolving into elitist and monolithic organization. ::scatches head:: Reading through the article, he doesn't seem to be very consistant with his views.
    --
    Entrepreneur : (noun), French for "unemployed"
    1. Re:Inconsistent Rant by Qzukk · · Score: 5, Funny

      he doesn't seem to be very consistant with his views.

      Actually, I think it's just the opposite. He's very consistent: "Everything sucks."

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
    2. Re:Inconsistent Rant by OglinTatas · · Score: 4, Funny

      "I guess someone should tell automakers that they should reinvent a mode of transportation from scratch. That four wheels, an engine, and brake and throttle thing is so passé nowadays. "

      It's been done. The Segway.

    3. Re:Inconsistent Rant by Pxtl · · Score: 4, Insightful

      Likewise, there was BeOS and Next, which were both good attempts to make new OS's, but fell flat because an OS is more than just a product - it's a platform, and platforms need a lot of inertia to survive - either from age, or from a big push from a lot of businesses. Next survived in OSX because Apple combined the innovation of Next with the Mac's inertia. BeOS had no such benefactor - it's still around as some small retail OS that nobody uses, and an opensource project with insufficient support.

    4. Re:Inconsistent Rant by QuietLagoon · · Score: 3, Interesting
      He's very consistent: "Everything sucks."

      Reasonable people adapt themselves to the world. Unreasonable people attempt to adapt the world to themselves. All progress, therefore, depends on unreasonable people. -- George Bernard Shaw

    5. Re:Inconsistent Rant by hungrygrue · · Score: 2

      Yea... The great Segway... As far as automobile alternatives, the Segway is silly. Interesting, but silly. I'll stick with a bicycle which doesn't need to be charged, is faster, has much further practical range, is *MUCH* lighter weight (a good road bike will not be much over 20 lbs), and can be bought new for a fraction of the cost or at a yard sale for a few bucks. This actually fits quite nicely with the original discussion, the Segway is revolutionary but not exactly useful. It is, in effect, made outdated by a technology that has been around since the late 19th century :-)

    6. Re:Inconsistent Rant by Iriel · · Score: 2, Interesting

      I noticed that Bob leaves a large hole in his attack on OSS. It is true in that most companies just want a shiny box and packaging with a guarantee that the vendor will fix everything without having to teach a class on it. However, just because software is OS doesn't mean it was sold by some college CS undergrad who forgot to spellcheck the readme.txt. Novell (for example) doesn't sell you a Novell enterprise desktop package for your business on an unlabeled Staples CD-R wth a note scribbled on the back.

      Companies like them use OSS to build enterprise level suites with support that are still usually (but not always) cheaper than an MS or Unix alternative. Then they compete in the market based upon the merits of a system that is 'rigorously tested and constantly updated by the top programmers in the world and maintained by our top-rated staff' as opposed to getting an operating system programmed by a bunch of college CS geeks.

      I think Bob needs to realize that companies don't need to know they're using OSS because a company that uses it can be every bit as professional as he thinks Microsoft is. If OSS doesn't work because it doesn't work for the consumer as well as Microsoft does, then why is that so many web servers are running Apache on (likely) some version of Red Hat?

      --
      Perfecting Discordia
      www.stevenvansickle.com
    7. Re:Inconsistent Rant by PlacidPundit · · Score: 2, Informative

      It's worth remembering, however, that NeXT was standing on the shoulders of giants with BSD and Mach. And the concept of Services was derived from pipelines in the CLI.

  2. Thoughts by AKAImBatman · · Score: 5, Insightful

    Windows is sort of a GUI version of the Mac's operating system, and Linux is of course Unix, which stems from 1968. These are both old clunkers. So the question is, Where are the new operating systems likely to come from?

    I hate to break it to Mr. Metcalfe, but most entities lack the resources to do a ground up rewrite of a fully featured Operating System. Simply writing a functional OS isn't the hard part. It's just a platform upon which software will be built. There were hundreds of OSes written between 1960 and 1990. During the '90s, however, computing platforms began to stabalize. Software was written that had a greater than 5 year life span, Operating System began to stabalize on a few "standards" (namely Unix/Vax/CPM derivitives), and massive amounts of time and money were invested into developing these platforms. Now we're standing on the 10,000 ft high towers we call Windows, Linux, and Mac OS X(NextSTEP) and we're looking at how difficult it is to replicate the decades of work that has gone into these systems.

    Building a more powerful and "correct" system would mean throwing away software such as OpenOffice, Mozilla, Quickbooks, Photoshop, Acrobat, etc. Software that took decades to build! Thus any future solution based on cutting edge CompSci Technology must either bite the bullet and rewrite these complex apps (good luck) or build in a translation layer that allows them to continue working. Neither choice is very appealing.

    The "third road" that is currently being explored is the road of running Virtual Machines on top of today's existing infrastructure. Java, .NET, and Mono are examples of the market attempting to find a way to combine modern technology with the tech of yesterday. Unfortunately, the results are less than stellar. For example, instead of aligning Virtual Memory along object bounds (a natural fit that could be done without hardware support), these systems must contend with the existing 4K VM implementations. Instead of running the protected code in a flat heap (which CAN'T break the memory model!) these systems must contend with the memory indirection that operating systems throw their way. The results of this poor matchup between machine and software is a performance penalty, both real and perceived.

    The Virtual Memory swaps more than it should. Object files are not shared. Memory usage is 20% greater than a native program. So on and so forth.

    A lot of research has gone into mitigating these issues (with Sun producing some very impressive results!), but it doesn't change the fact that the machine and software are mismatched. That mismatch discourages companies from writing new applications in these managed environments, where they would be free from the bonds of traditional OS designs.

    My gut says that a rather major shift in how we use our computer will have to happen before we can truely replace the systems we have today.

    I'd like to point out that two major pieces of infrastructure were left out of the Internet when it was being built--largely because it was built by graduate students (and people like graduate students). They left out security and economics. So we have the spam problem (which can be traced directly to the lack of concern for security), and we have IP rules that are in flux because the Internet doesn't have the right tools for monetizing various activities. So we're busily trying to put security and economics into the Internet.

    In all honesty, the Internet never would have been as successful as it was if it wasn't for the freedom it provided. Many other networks offered these features, but they were eventually usurped by the Internet.

    Hindsight is 20/20. Had the BSD/ARPANET folks attempted to address these issues back when it was created (which would have been ludicrous given its Military intent), their solutions would have likely been wrong. Keep It Simple Stupid. It may not be the best solution, but it's the most effective solution.

    P.S. In case of Slashdotting, break glass

    1. Re:Thoughts by MosesJones · · Score: 4, Insightful

      During the '90s, however, computing platforms began to stabalize. Software was written that had a greater than 5 year life span

      Err I'd say that less systems written in the 90s lasted over 5 years than the big old monoliths of mainframes and COBOL, which developed in the 70s and 80s gave us Y2K.

      Long-life software wasn't new in the 90s, and the old stuff rarely runs on Unix or Windows....

      --
      An Eye for an Eye will make the whole world blind - Gandhi
    2. Re:Thoughts by ratta · · Score: 2, Insightful

      You're surely right, but don't forget what Apple did with OS. They rewrote a major part of their OS, and now for them it is even easer to use Forefox, OpenOffice, etc. It was a really smart move.

      --
      Wondering why i am doing so strange posts? I am trying to get a "+5,Flamebait" or "-1,Insightful" rating.
    3. Re:Thoughts by iwadasn · · Score: 2, Insightful

      Good points all around, I'd like to just add a few things...

      First of all, a massive reimplementation is underway. Software is migrating to VMs at a fairly impressive pace. The only ones who seem to be holding out are the shrinkwrap vendors, but even then are starting to buckle. When Microsoft moves significant code to .NET (if it ever happens), the others may move as well.

      Already, custom coded apps are almost always writting in Java, or (shudder) VB and .NET. When this increases further, you can probably expect to see the VMs take over, relegating much of that 30 year old code to the dustbin of history. After everything is VM based, the virtual memory will probably also head for the trash heap, and hardware would likely become much cleaner and simpler.

      I'm mostly disappointed with Apple for holding off on this to the degree that they have. Java is a natural fit for them. Write a VM that looks and feels native, then make all their apps in Java and sell them on windows as well. By blazing the trail they might be able to get others to similarly write in java, and level the playing field for themselves. If the linux geeks would bury their long held animosity, then they could make a similar move, and attempt to take a real position on the desktop. Instead, they thrash against a a technology that is not only a natural fit for them, but is also, almost indisputably, the future, and they remain relegated to server closets where the admins install java on them anyway and they are workhorses for JBoss. Grow a brain guys.

  3. Where? by derEikopf · · Score: 4, Insightful

    Where are the new operating systems likely to come from?

    They aren't going to come until we get past "old" technology like monitors, keyboards, and mice.

    1. Re:Where? by Otter · · Score: 2, Insightful

      Basically, things are on hold pending an order-of-magnitude increase in computational power, pervasive wireless, voice recognition that works and several other things. As you say, there's no compelling reason to replace WIMP and everything that's grown up around it, if you still need to read passwords off the sticky under your keyboard before typing them into your big beige box.

  4. PHBs, open source and commercial interests by itsownreward · · Score: 4, Insightful
    While talking about operating system innovation coming from companies rather than open source, Metcalfe said:
    "I'm thinking of investing in a company that sells software, and its competitors are open source. I've been speaking to the company's customers and asking them why they'd buy this software instead of just taking the open source. Their answer: 'We don't want to learn about the software, and we need it serviced and supported, so we're going to buy it from this company instead of taking it free from the open-source community.'"
    I work in a healthcare organization's IT department. We have vendors that go out of business or stop offering products we've come to depend on, but then offer an "upgrade" that will cause us to change our entire workflow. Therefore, we make sure we know our systems intimately so we don't get burned. We're largely a Microsoft shop, but I am slowly pushing a bit of open source in there. I guess there's truth in Mencken's saying, "No one ever went broke underestimating the taste of the American public." I guess that goes for its laziness, too.
  5. Clunkers? by erroneus · · Score: 2, Interesting

    Okay, while I'll agree that the technology and underlying philosophies of design are "old" in technology years, but for something to be an "old clunker" there should be a basis for comparison -- something that is NOT an old clunker. What is that something? Anyone have any examples?

    1. Re:Clunkers? by AKAImBatman · · Score: 5, Informative

      Mac OS X has one foot in the past (FreeBSD) and one foot in the future (Mach). Between the two of them, OS X is a bit more futuristic than its competitors. However, a machine that died before its time was the Symbolics LISP machines. I've never had the opportunity to use one, but my understanding of these machines is that they never needed any of the "modern" processor or software concepts we use today, because the underlying software system (LISP) was incapable of creating the types of memory corruption we try to prevent even today. And if a program blew up, you could actually modify its memory image on the fly and continue its execution.

      On top of everything, the hardware architecture was much faster than contemporary computers due to its LISP oriented design. Apparently, a good portion of the LISP language was able to execute directly in the hardware!

      At least, that's how I understood it. Sadly, it didn't get much attention outside of academia. :-/

    2. Re:Clunkers? by CyricZ · · Score: 2, Interesting

      Why the various Lisp machines did it not make it outside of academia? It is because most programmers simply cannot handle functional programming, even when using a non-pure functional, semi-imperative language such as Lisp. The pool of programmers capable of developing for such a system is quite limited, as as such they will cost far more to employ.

      Why should a company spend a massive amount of money on a Lisp-based (ie. at the hardware level) system and developers for it, when they can toss together a very powerful PC and Visual Basic code written for pennies or pence by some offshore programmer.

      It's all a matter of economics. Technically, such a system is very sound. Economically, it just plain isn't worth it. Unless similar machines could be developed which included massive technical benefits over existing systems, they will not become popular.

      --
      Cyric Zndovzny at your service.
    3. Re:Clunkers? by frankie · · Score: 2, Insightful

      No, that would be one foot in the living past (FreeBSD) and one foot in the dead past (Mach). Mach is considered a bad kernel design by both theorists and developers. The only reason Apple used it instead of a plain BSD kernel is Avie Tevanian and the NIH syndrome.

    4. Re:Clunkers? by jacrawf · · Score: 2, Funny

      Because Emacs already is an operating system.

    5. Re:Clunkers? by convolvatron · · Score: 3, Interesting

      here you are wrong. did you ever use one? the symbolics was by far the most usable and productive machine at the time.

      its primary strength was exactly that you could toss together something pretty nice in basically no time at all.

      dont you think it might have something to do with marketing, barriers to entry, and culture? there is nothing fundamentally economic about the failure of symbolics (except the barrier to entry bit, the volume was so low that they were very expensive machines)

  6. The new OS by pupeno · · Score: 3, Informative

    Everybody complains about Linux and Window and all the other operaitng systems about being old an obsolete but I see only a few putting effort in building new operating systems like what Slate can become (in the long term) or what Movitz is aiming.

    --
    Pupeno
    1. Re:The new OS by CDarklock · · Score: 2, Interesting

      Building a new operating system takes a long time and a lot of money.

      Because Windows comes on pretty much every new PC, and Linux is readily available for download, you will probably never get that money back.

      OS/2 was a superior operating system to Windows 95, but people didn't buy it. They bought computers with Windows, or they installed Linux from cheap CDs (downloading it wasn't feasible at the time for most people). Now the superior O/S is being folded up and thrown away.

      So what about the hardware question? NeXT was a superior operating system on superior hardware. First they stopped making the superior hardware, then they stopped making the superior O/S. Why? No money in it.

      Has the world changed? Be was a superior operating system on superior hardware. First they stopped making the superior hardware, then they stopped making the superior O/S. Why? No money in it.

      The open source community has some pipe dream that when you can't make money from software, you will contribute your software for free. What actually happens is people stop writing software so they can do something that makes money. And for all the rhetoric about freedom, your scads of users aren't really going to matter when the project has only two developers left working on it... and both of them are investing most of their effort in something profitable.

      That's why I believe in the BSD license. Code under the BSD license can still be commercially exploited. That means you can still make money off it. And that means smart people will continue to write and use it.

      --
      Microsoft cheerleader, blue flag waving, you got a problem with that?
    2. Re:The new OS by Golias · · Score: 3, Interesting

      So what about the hardware question? NeXT was a superior operating system on superior hardware. First they stopped making the superior hardware, then they stopped making the superior O/S. Why? No money in it.

      Actually, they are still making a superior OS on superior hardware. They didn't go away, they took over Apple from within.

      I think it's one of the most fascinating stories of the last 20 years how Steve Jobs somehow managed to steal his old company back.

      --

      Information wants to be anthropomorphized.

    3. Re:The new OS by ShieldW0lf · · Score: 4, Insightful

      The open source community has some pipe dream that when you can't make money from software, you will contribute your software for free. What actually happens is people stop writing software so they can do something that makes money.

      That's such a load of bullshit. I take the free enterprise stack. I sell clients on my ability to develop software that will fix their problems using the free enterprise stack as a base. I discover that the free enterprise stack doesn't have some feature I could really use to more effectively service these clients. So I write the new feature. And I deliver a solution to them that works. Now I've got this new feature in the stack, I can't really sell it to anyone on its own, and if I don't roll it back into the main trunk, I'll have to maintain it if I ever wish to use it again. So I give it back to the community because it's in my best interest to do so. This is how the software gets contributed for free. One itch at a time. And you can spout off all your rhetoric about the "open source pipe dream", but that's all it is, spouting off. It exists, it progresses, it takes market share from the most powerful company on earth, and it appears to be gaining momentum. The existance of the thriving community is PROOF that you are wrong.

      --
      -1 Uncomfortable Truth
  7. Oh the irony by DarthVeda · · Score: 5, Funny

    That a site called Always On has been slashdotted.

  8. I'd get some better info if I were him by ravenspear · · Score: 2, Insightful

    Windows is sort of a GUI version of the Mac's operating system, and Linux is of course Unix, which stems from 1968.

    Huh?

    Since when has the Mac operating system not have a GUI or since when has Windows been more GUI like then the Mac OS.

    Also the Mac operating system has a heck of a lot more in common with both Linux and Unix than is does with Windows. In fact if you want to say anything about comparing GUIs, it would be far more accurate to say that the Mac operating system is a GUI version of unix and Windows is a GUI version of DOS.

  9. His comments on open source... by tcopeland · · Score: 4, Interesting
    ...are interesting:
    Because modern software corporations know how to align the interests of the people. They know how to motivate people. They know how to sustain themselves over a long period of time, whereas I'm suspicious about the motivational structure of an open-source community and wonder whether it's sustainable.
    That's an understandable suspicion. On the other hand, if you're using an open source product to help build your company, it's in your best interests to take some interest in that product and to help it develop. Then you're part of the community and you know how things are going.
  10. Before OSes can be innovative, languages must be by cscalfani · · Score: 4, Interesting

    Before we can ever hope to innovate the OS, we must first innovate software development, i.e. languages.

    All the language techniques that we use are rooted in old technologies. Its still just as hard to code today as ever, if not harder.

    I've been programming since 1980 and back then you wrote everything yourself. It was a lot of work but at least you controlled the quality of the system because you wrote it all.

    Today, systems are so complex (unnecessarily so), and the technology hasn't changed enough to keep up with the demand. We still write for loops like we always have.

    The spoon is a fine tool when all you dig are holes in ice cream but when you have to dig a trench in the ground, forget it.

  11. 1337 by bellmounte · · Score: 3, Funny

    I think what he is hinting at is computers need to be based on the wonderful new technology known as leet speak. It would make them so much more efficient.

    Until then, I'm just going to go pwn sum nubs.

  12. Re:New OS by tomstdenis · · Score: 4, Insightful

    Actually this is bs. The majority of us OSS folk are writing ***PORTABLE*** tools that work anywhere. This is why you see firefox on mac, win32, bsd, linux, beos, etc...

    This is why you see GCC on mac, win32, bsd, linux, beos, qnx, etc...

    This is ... and so on ...

    Only lame arrogant windows developers think that "linux using folk only write for linux".

    Heck some of the places my software has and is being used doesn't even have a proper OS [e.g. PS2 and Gamecube].

    On topic again, as the "inventor of ethernet"? What the fuck does that mean? It's not that impressive. I mean it's useful but so is sliced bread and we don't honour that guys name either! He did his part to make the world better. Groovy. Now step aside and stop milking something you did nearly a decade BEFORE I WAS BORN.

    Tom

    --
    Someday, I'll have a real sig.
  13. Backwards thinking by sugarmotor · · Score: 2, Insightful

    Quoting Bob Metcalfe: [...] Private property is a great technology [...] This is backwards thinking, sloppy thinking, boring thinking. The big problem with the "private property" myth is that over time property accumulates in the control of few. This is a huge problem in the face of the goal of economic justice. What is Bob Metcalfe's answer to that?? His remarks about big corporations knowing "motivation of customers" and "motivation of employees" are completely misguided. On the side of the customers, we're looking at mega-advertising campaigns. On the side of employees we're looking at union-busting and the like. This is not brilliant, this is crude stuff. Stuff that we can do without. The rest of the interview is just boring.

    --
    http://stephan.sugarmotor.org
  14. Old is better by Neil+Watson · · Score: 2, Interesting

    While today's software is good I think some 'old' things from the past should be revived. We just don't make software like we used to. Large amounts of memory and CPU cycles have made us sloppy. Those people that designed software for a few kilobytes of RAM we smart.

    1. Re:Old is better by Anonymous Coward · · Score: 2, Insightful

      I'm not sure that its necessarily made us sloppy, but rather we are doing more things at a higher level. Sure sloppiness and bad algorithms do play a factor. But think about what some of the software we use is doing compared to that older software.

      Our programs today have better interfaces and more functions than programs of yesteryear. Think of what you can do with OpenOffice or Microsft Office these days, compared to in the past. We're streaming video, storing huge amounts of data, managing disperse systems, pushing the latest and greatest graphics. Compare that to 10 or 15 years ago.

      That said, we're definately using a disproportionately large amount of CPU and RAM. But the thing is that we're not throwing it away. A lot of it goes into making higher level languages that allows us to build bigger and better systems easier. We have things like garbage collection, object oriented programming, and APIs with general-purpose data structures that allow us to rapidly develope systems.

      I bet that you could probably re-implement a lot of those general purpose data structures in a lower level language so that they run faster, but you'd have to spend time, the most precious of resources, to do so. Given a long enough time you could reimpliment the latest and greatest games in Assembly language, and improve their performance. But it would take you much much longer, and probably make bug fixing orders of magnitude harder.

      We're not throwing away those CPU cycles and memory to sloppy code. We're trading them so that we can build larger, more powerful, and more secure programs quickly and with less bugs.

  15. Nothing to see here, move along by $RANDOMLUSER · · Score: 5, Funny

    He's just trolling. He has a pathological need to pop up every once in a while and say "You know I invented Ethernet, don't you?"

    --
    No folly is more costly than the folly of intolerant idealism. - Winston Churchill
  16. GUI version of MacOS by MECC · · Score: 4, Insightful

    "Windows is sort of a GUI version of the Mac's operating system"

    As opposed to the non-gui version of Mac's operating system....

    --
    "We are all geniuses when we dream"
    - E.M. Cioran
  17. Power Mongers Go Where the Power Is. by darkonc · · Score: 4, Interesting
    The Internet has arrived, and all of those people are now just like ITU: IETF has become the ITU."

    Not a big shock... about 15 years ago, the two power centers in BC Politics were the NDP and the Social Credit Party.. The left wing was in the NDP who had power at the time, and the Socreds had pretty much lost favour as the reigning right-wing party (( yeah that belies their name, but having been decades in power, the right wing had taken them over )). Then an upstart Liberal party maaged to worm their way into the leaders debate and caught fire, becomming the official opposition.

    By the next election, the formeer Socred political machine had taken over the Liberal Party and kicked out it's leader. These are the people who now run the province.

    The problem with our political/media system is that the only people who tend to end up in positions of power are those who really want it (and are willing to do whatever it takes to get that power). Unfortunately, these are precisely the people you don't want in power.

    --
    Sometimes boldness is in fashion. Sometimes only the brave will be bold.
  18. The IETF is no longer an Engineering organization by wayne · · Score: 4, Informative
    I can't read the "always-on" story because it is slashdotted, but I'll comment on the IETF becoming the ITU.

    AMEN!

    As someone who has recent scars (SPF, MARID) from dealing with the IETF, it is clear to me that they are no longer an engineering organization, but rather a highly political one. No longer is there much concern about adopting patent encumbered technology into key Internet protocols (MS SenderID) like they used to object to things like the RSA patents.

    Instead, the IESG is actively working to push through this patented technology by shutting down the MARID WG so that they can advance the SenderID proposal without any public review. More over, the IESG has declared that it is ok for the SenderID spec to re-use SPF records in incompatible ways, that the SPF RFC must be held back until MS is ready ("to be fair to MS"), and the IESG is going to ignore the last 1.5 years of SPF deployment experience and start fresh with collecting data since MS has only recently started doing SenderID checking (again "to be fair to MS").

    The IETF needs to take the "E" out of their name and become the Internet Political Task Force.

    --
    SPF support for most open source mail servers can be found at libspf2.
  19. Stay in the swamp by RealProgrammer · · Score: 4, Insightful

    You invented ethernet. Even before that, you were THERE, and helped operate, the first big ARPANet demo for Congress. You founded 3Com. You wrote more Inforworld columns than a mere human like me could read. You are the Old Master, Yoda in the swamp.

    Don't spoil it now by being Dvorak. Please.

    Linux is only Unix on the outside. There's scarcely little code on the inside from 1992. And I believe there is none (zero, nada) from before 1975. I know this because I've looked at the early UNIX code at http://tuhs.org/ and what little survives is not found in Linux.

    Windows a copy of the Mac? In the sense that English is a copy of French, maybe [flames >/dev/null]. Some elements are the same, but how you do things with them is quite different.

    Asking what the new OS will be is asking the wrong question. Ask instead what new class of devices will need an OS, and the answer would follow from that. I say "would" because I'm not sure even that question is relevant.

    --
    sigs, as if you care.
  20. This Doesn't Work by eno2001 · · Score: 4, Interesting
    Metcalfe: Well, anonymity cannot be the rule. Anonymity has to be the exception. You should allow people to be anonymous if they want to, but the general rule shouldn't be anonymity, which is the present case. The source field of every packet in the Internet goes uninspected. You can cram anything you want into that and generate denial-of-service attacks (just to name one).

    If networks were configured so that the "general rule" is NOT to be anonymous, then there is no way you can guarantee true anonymity. The reason being that if someone wantred to be "anonymous", they would have to request that privlege from some kind of "anonymity broker" or... own their own network. And even then, with the ability to track the packets, the only guarantee of anonymity is not technical, but social. The owner of the network that the message originated from would have to be the barrier. And as we all know, the current political climates around the world will be unlikely to respect that anonymity if they decide that your activities are "illegal". If someone wants to send e-mail saying they hope that a certain politician gets assainated, in some locations, that would be "illegal". Even though it's really freedom of speech. So, I don't think his suggestion works because it's not true anonymity unless you are in a very powerful position. Every citizen (from beggar to king) should have access to anonymity.

    --
    -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
  21. Um, and so they should. The automobile is obsolete by Colin+Smith · · Score: 4, Interesting

    "I guess someone should tell automakers that they should reinvent a mode of transportation from scratch."

    Perhaps transport engineers rather than automakers. The automakers have a huge investment in the status quo. You don't need 4 wheels an engine, brakes, throttle or even a driver.

    Transport engineers have already designed and built transport systems which don't have any of the above. Starting from scratch in the 1950s they devised a transport system which optimises the mathematics of getting from A -> B. Yes there is mathematics which describe the performance of transport.

    It turns out that this is about as close to optimal as you're going to get with current technologies. Computer controlled, linear induction motors, a few rollers rather than wheels and only 16 moving parts. Non stop from A->B, no congestion, no traffic lights, no changing routes, no waiting on schedules.

    It's been independantly re-invented a few times over the last few decades but we've now got the computer technology to actually do it.

    --
    Deleted
  22. Red Swingline by Dolly_Llama · · Score: 4, Funny

    How is the red swingline a symbol for IT? Cubicle farms, office bs in general i see, but how IT?

    Milton was entirely ineffectual. Do IT workers sympathize with him for being victimized or is the red swingline a passive finger to the man?

    --

    Somewhere, something incredible is waiting to be known. -- Carl Sagan

  23. BeOS was innovative by m50d · · Score: 2, Insightful

    Look where that got it. Until the apps demand innovation for what they want to do, we won't see innovation in the OS sphere. Dos programs were making GUIs and using the mouse before GUI operating systems became popular.

    --
    I am trolling
  24. Re:GUI version of MacOS by angusmci · · Score: 2, Informative

    MECC wrote:

    As opposed to the non-gui version of Mac's operating system....

    I guess that would be Darwin.

  25. Mach is hardly the future. by CyricZ · · Score: 2, Informative

    You do realize that Mach is 1980s technology, correct? Even stuff like today's Cocoa was mostly developed in the late 1980s and early 1990s. While Mac OS X is a fantastic system, it is hardly "futuristic", as you incorrectly claim.

    The thing with Mac OS X is that it does not have the cruft of other systems. Hardware wise, Apple is willing to force their consumers to eliminate the old (ie. floppy drives) and to proceed with the more modern (ie. FireWire). But the more modern technology is hardly futuristic. Mac OS X is still solidly based on software technology that is at least 15 to 20 years old, it not more.

    Don't confuse "modern" with "futuristic". You'll never find "futuristic" items available for sale today.

    --
    Cyric Zndovzny at your service.
  26. Easier answer than all that by WindBourne · · Score: 2, Insightful

    *nix is a kernel in which different underlieing designs and applications can be easily added. That is why *nix survives.

    MVS, which was the original stable OS (not huge changes since the 60s) made it difficult to change out things (and very expensive).

    As to the VM world, yeah, that should introduce us to a load of new changes.

    --
    I prefer the "u" in honour as it seems to be missing these days.
  27. Christ on a bike... by thewils · · Score: 2, Insightful

    I can't even get drivers for my 64-bit Clunker. Do you think manufacturers would want to start supporting a raft of other OSes?

    --
    Once I was a four stone apology. Now I am two separate gorillas.
  28. Copy of Article by billstewart · · Score: 2, Informative

    This is the second part of a four-part conversation between AlwaysOn editor-in-chief Tony Perkins, managing editor Rich Seidner, and Bob Metcalfe, the inventor of Ethernet and former CEO of 3Com who's now a general partner at Polaris Ventures. In Part 1, Mr. Metcalfe talks about the next big thing for the Internet (video); in Part 3, he tells the story behind Metcalfe's Law; and in Part 4 he tackles the blogosphere.

    Internet Security and the Threshold of Pain

    How bad do things need to get for organizations to be willing to switch to IPv6? Very, says Ethernet inventor Bob Metcalfe, who nonetheless believes that the time has come.

    Bob Metcalfe [Polaris Ventures] | POSTED: 07.18.05 @08:20

    AlwaysOn: I want to talk about open source. Our view is that open source is a metaphor for a lot of things. And it's all because Metcalfe's Law is finally coming into full bloom--because everything's on the network. Community is becoming really important, and people are sharing and uploading everything from photographs to blog posts. What are your thoughts in this area?

    Bob Metcalfe: I'd like to point out that two major pieces of infrastructure were left out of the Internet when it was being built--largely because it was built by graduate students (and people like graduate students). They left out security and economics. So we have the spam problem (which can be traced directly to the lack of concern for security), and we have IP rules that are in flux because the Internet doesn't have the right tools for monetizing various activities. So we're busily trying to put security and economics into the Internet.

    This is a little bit counter to the open-source mentality. You have to be careful, however, because open source isn't one group. There are a bunch of different, contending open-source groups. For example, the free-software people shouldn't be confused with everybody else in open source.

    I think the problem with open source is that it doesn't quite have its economics worked out. There need to be ways to own things. Private property is a great technology; it's probably one of the major tools the West has. By granting private property to people, you stimulate economic growth. And I think the same thing applies to software. So open source will have to figure out how to get monetized to protect property over time.

    If you look at Windows and Linux, both are based on 25-year-old technology. Windows is sort of a GUI version of the Mac's operating system, and Linux is of course Unix, which stems from 1968. These are both old clunkers. So the question is, Where are the new operating systems likely to come from? And will that OS come from the modern software corporation (of which Microsoft is the epitome), or will it spring out of some open-source initiative at some university somewhere? My bet is that the modern U.S. corporation--like Microsoft but not Microsoft in particular--is much more likely to come out with this new OS than a loosely coordinated band of volunteers in the open-source community.

    AlwaysOn: Because?

    Metcalfe: Because modern software corporations know how to align the interests of the people. They know how to motivate people. They know how to sustain themselves over a long period of time, whereas I'm suspicious about the motivational structure of an open-source community and wonder whether it's sustainable.

    I'm thinking of investing in a company that sells software, and its competitors are open source. I've been speaking to the company's customers and asking them why they'd buy this software instead of just taking the open source. Their answer: 'We don't want to learn about the software, and we need it serviced and supported, so we're going to buy it from this company instead of taking it free from the open-source community.'

    In that case, it's the motivation of customers. A little earlier I was talking about the motivation of employees:

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  29. Re:New OS by arkanes · · Score: 2, Informative
    Due largely to the popularity of Windows, almost every signifigant Linux application is ported to Windows. The exceptions are when it requires low-level systems knowledge or integration thats harder or impossible on windows (stuff like efence), or when the Linux software was addressing a need that had been fulfilled in Windows (KDE/Gnome, for example).

    The *vast* majority of the software I use runs on at least 2 platforms, one of which is Windows. The exceptions are almost always Windows only.

  30. Different "anonymity". by khasim · · Score: 4, Informative

    Bob is talking about packets using faked source addresses.

    These are useless for anything other than a (D)DoS attack. They are useless because a connection cannot be established and no data can travel.

    It is easy to have personal anonymity, but still have the first upstream router check the source addresses to make sure they are legit. But it depends upon someone, somewhere being willing to /dev/null his logs on a continuing basis and both sides using encryption. As you said, this is not technical, but social.

    There is NO reason for the source address to not be confirmed by the upstream router.

    There are LOTS of reasons for personal anonymity to be maintained. And we can have personal anonymity even if we confirm the source addresses of packets.

  31. Re:WTF is he saying? by Spiderfood · · Score: 2, Insightful

    It's interesting how people are fixating on this comment. In context, it is certainly clear that he knows the differences and similarities between Windows and Mac. That he chose to speak sloppily in this regard is not something people seriously should be chewing on. As a point of argument, he statement does not strictly imply that MacOS is NOT a GUI. What he is stating is the Windows is a GUI, and, in his mind, an evolution of the Mac operating system.

    --
    + Spiderfood
  32. Where? by Spazmania · · Score: 2, Interesting

    Where are the new operating systems likely to come from?

    Where are the new wheels likely to come from? I mean the wheel was invented by the cave man and tires have been around since the 19th century. So who will make a better wheel?

    Maybe Unix is still around because back in 1968 those engineers got it right. Maybe there aren't any revolutionary OSes around the corner -- just evolutionary changes to the ones we have.

    --
    Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
  33. Personal Rapid Transit? by Grendel+Drago · · Score: 2, Informative

    That's first one is a horribly designed website. But it's a pretty interesting idea; it'd certainly be a good idea for cities. Perhaps it could be run like the subway or other public transit systems currently are. I'd certainly like to see how a real public trial would work out.

    And hey, there's an article.

    --grendel drago

    --
    Laws do not persuade just because they threaten. --Seneca
  34. NeXT is UNIX; NeXT is the MacOS by peter303 · · Score: 2, Informative

    First NeXT is not dead. It morged with the MacOS when Apple acquired NeXt (or the other way around).

    NeXT orignated from a fourth strand of UNIX (not ATT, not BSD, not Linux). Carnegie Mellon wrote a highly layered version of UNIX called the Mach microkernel. Conventional UNIX was sinking under weight of trying to do to much in the kernel.

  35. Re:Um, and so they should. The automobile is obsol by Colin+Smith · · Score: 2, Informative

    " I'd hate to get into one of those cars after some bozo has barfed"

    You don't need to. The Taxi2000 system has a reject button. Reject the car and a replacement arrives a few seconds later, the soiled one heads off to the depot for cleaning.

    --
    Deleted
  36. Re:Um, and so they should. The automobile is obsol by Colin+Smith · · Score: 2, Insightful

    "And how will these wonderful trolley cars get me around to these various destinations with my cargo."

    It is a network transit system, the track is laid out more like a grid than a corridor. It'd get you directly to your destinations because there would be stations nearby.

    e.g.
    http://www.swedetrack.com/city7.gif

    --
    Deleted
  37. Re:Um, and so they should. The automobile is obsol by 4of12 · · Score: 3, Interesting
    The automakers have a huge investment in the status quo.

    Considering suppliers to the automotive industry, the jobs they provide, the petroleum products required to make them run, and that much freight moves by trucks, the investment by society as a whole is huge.

    Which is why it's going to be increasingly traumatic as the oil faucet slowly begins to close. Geopolitics surrounding petroleum is already traumatic enough now, thank you.

    --
    "Provided by the management for your protection."
  38. Lisp by RAMMS+EIN · · Score: 3, Interesting

    Indeed, Lisp does not suffer from the problems that cause the lion's share of security breaches today. At the same time, Lisp pioneered many concepts of modern programming languages (even if they weren't all invented on Lisp), and then some. Garbage collection, Lisp macros (which allow you to extend the syntax of the language), functional programming, and object-oriented programming are all common practice in Lisp, just to name a few. All of this (maybe not OO - I'm not sure if it had been invented yet) worked very nicely on Lisp machines, and I think they even had some sort of GUI, although it wasn't like the GUIs of today.

    Lisp machines failed mostly because Symbolics tried too hard to make money off them. They made them very expensive, so people bought cheaper hardware and lived without Lisp. In the meantime, they protected everything with patents and copyrights, and since Symbolics folded, nobody seems to have been able to re-create the technology.

    It is worth knowing that the GNU project was started pretty much as a direct reaction against the Symbolics affair. A certain hacker called Richard Stallman worked at Lisp Machines Inc., the other company that made Lisp machines, and was so upset about the abuse and destruction of this good system for the sake of commercial interests that he decided to build a system that would be Free and remain Free. Indeed, Lisp was mentioned as an official language for the GNU system (the other one being C), although few programs are written in it (Emacs and Sawfish come to mind).

    Lisp still survives as a language (I think it's the second oldest programming language), and the community seems to be reviving a bit, although many lispers seem to "make do" with languages like Ruby and Python, that have a somewhat lispy feel to them. And with projects like Movitz, maybe we will have lisp machines again someday.

    --
    Please correct me if I got my facts wrong.
    1. Re:Lisp by mrdlinux · · Score: 4, Informative

      There were a number of Object Oriented systems written on top of Lisp; because Lisp allowed such flexibility in the language.

      Genera, unless I'm mistaken, was based on Zetalisp (LispMachine Lisp) with an object system named "Flavors", a message-passing system with mix-ins loosely based on Smalltalk. The GUI was written with this system, and the GUI itself was interesting because its introspective abilities closely mirrored that of the underlying language. The elements of the GUI were all objects that could be manipulated, selected, inspected. Even graphical and text output on the screen could be categorized into classes and later manipulated as objects. This became the basis for CLIM (Common Lisp Interface Manager).

      Unfortunately this style of GUI has fallen to the wayside in favor of the simpler but stupider Windows-style one. C and C++ do not have the flexibility that is required, in any case, for a dynamic GUI like that on the Lisp Machine. Look to Smalltalk, Squeak, Slate, or the reinvigorated CLIM projects (McCLIM, FreeCLIM) instead.

      Symbolics made bad business decisions, indeed. They still do exist, and even have the oldest .com name registered: symbolics.com. There is hope that someday all the thousands of man-hours of work on Genera will become unencumbered or re-released.

      Stallman helped popularize Emacs, along with the free software movement, which developed in parallel with the similar editors of the Lisp machines. The problem with Stallman is that he is incredibly stubborn (no kidding), and made mistakes early on that he was unwilling to fix. Hence FSF Emacs and even XEmacs is crippled as an editor, a language, and a platform, though people who only make simple use of it might not understand why.

      It is just as well that Lisp languished in FSF, because it sprouted elsewhere in the open source community, with no philosophical encumbrances which don't necessarily make sense in a dynamic environment like a Lisp.

      Over the last five years, I've seen quite a revival of Lisp. The regular programming crowd slowly accepts new ideas; they still insist on making the same mistakes that were already passed by Lisp programmers years ago. Ah well. My job is working on systems in Common Lisp, I am happy.

      --
      Those who do not know the past are doomed to reimplement it, poorly.
  39. Re:Um, and so they should. The automobile is obsol by Colin+Smith · · Score: 2

    Um. You're aware that you will have to pay for the use of the system?

    Taxi's that go to the depot for cleaning would only be unavailable until the service personnel at the depot had checked it. In the meantime there would be hundreds or thousands of other vehicles available to everyone else on the rest of the network. The only person who'd be inconvenienced is the guy who'd paid to stand and press the reject buttons on the taxis as they arrive.

    --
    Deleted
  40. Bicycles aren't optimal by Colin+Smith · · Score: 2

    "Ever tried a bicycle?"

    15 miles/day, 5 days/week. But it's really too slow for most people, the practical limit is about 10 miles. Then there's weather, traffic, sweat, clothing etc. Not exactly non stop either, certainly in UK you are expected to obey road traffic laws, that means traffic lights.

    --
    Deleted
  41. Re:Before OSes can be innovative, languages must b by cscalfani · · Score: 3, Interesting

    I think that systems are complex because of bad design first and bad implementation second. If you have a bad design, no amount of good implementation is going to save you. If you have a good design that's poorly implemented, then there was no point of having a good design.

    As far as languages are concerned, you could implement an object oriented approach to a C program (good design, bad implementation), but it is much easier to design a language that embodies that approach, i.e. C++.

    I've spent most of my 23 years programming, designing systems. Every time that I go the extra mile to do the best design that I can with the time allotted, the programming is simplified and complexity is reduced.

    Good designers see everything the same, good programmers see everything different. The best designs have their complexity in the structure not the code. Most systems have their complexity in the code.

    What are the problems today in languages that cause complexity in coding? Inheritance, garbage collection, OO languages that break encapsulation (.NET, Java, any programming language that uses GC), multiple objects being "owned" by more than one other object, multi-threading locks that are defined at programming level instead of structural level, etc.

    What I'm tired of seeing in "new" languages is the same old same old. Sure the syntax is different or some esoteric problem that the language designer had implementing a particular system in an existing language has been solved by their "new" language. But the basic concepts are identical to most existing languages.

    The only real innovation, (if you can call it that), that's been made in a recent (10 year old language) mainstream language, viz. Java, is by making INTERFACE a language element. Granted, interfaces have been around forever, but Java is the first mainstream language to implement it at the language level.

    What is needed is someone to completely throw out everything they thought they knew about languages and start from scratch using everything they know about complex system development.

    You may ask yourself, "Why don't I do this?" Because there's no money in it and once I did, I'd have to convince the religious to convert. Not worth it.

  42. Noooooo, not run like current public transit. by Colin+Smith · · Score: 2, Interesting
    Current public transit is horribly undesirable.

    You basically have to subsidise it to around about 50% in order to persuade people to use it. The UK subsidises the rail system to the tune of around £4 billion a year (approx $7 billion). This is largely because all current public transit systems are designed to carry groups of people from A->B.

    • Groups of people means stopping at every station to pick up and let off passengers, which means very low average speed.
    • Groups of people mean schedules in order to pick them up. Schedules mean more waiting.
    • Groups of people means the route can only go in the general direction they want to travel, which also means that they then have to make additional journeys some other way after getting off.
    • Groups of people means large vehicles capable of carrying large numbers. Which means large infrastructure to cope with the vehicles, which means expensive vehicles and expensive infrastructure.

    All of the above mean that current public transport is a dreadfully slow and expensive method of travel. Is it any wonder at all that people don't like current public transport and would rather sit in a congested traffic jam?

    Personal Rapid Transit should manage to be cheap enough to run at a profit and still attract passengers because it's way faster than the rest, including cars, there's no drivers to pay, the infrastructure is cheaper to build than a road.

    --
    Deleted
    1. Re:Noooooo, not run like current public transit. by JanneM · · Score: 2, Insightful

      When talking about subsidies of rail and mass transit, it's easy to forget the extent to which automobile transport (and aircraft) are subidized as well. You do not pay the full cost of using your car yourself, anymore than you pay the full cost of using a subway.

      Which is fine, of course; reliable, efficient transportation is hugely important to society, too important to leave to the vagaries of the market. And it's important to have a combination of sysetms, so you're not putting all your transportation eggs in one basket either.

      --
      Trust the Computer. The Computer is your friend.
  43. Re:Um, and so they should. The automobile is obsol by ipjohnson · · Score: 2, Interesting

    After reading the web site you sent out about the PRT I realized the prototype is in the back of parking lot 3 at raytheon's site in marlboro MA (where I worked for 3+ years) and I can tell you point blank the project died years ago.

    They can't even fire it up because the mice have chewed through most of the wiring. Rumor has it the last time they fired it up (5+ years ago) the PRT actually got stuck on the track and the people where left there for 2 hours while they tried to fix it.

    On a side note I actually used to park my car under it :)

  44. Re:Um, and so they should. The automobile is obsol by cayenne8 · · Score: 2, Insightful
    "And how will these wonderful trolley cars get me around to these various destinations with my cargo."

    ..."It is a network transit system, the track is laid out more like a grid than a corridor. It'd get you directly to your destinations because there would be stations nearby."

    I'm not sure you answered the GP's question. This was the first thing that occured to me. I buy groceries once a week...I fill up the front seat and floorboard of my car easily...and if I buy charcoal, and a couple of other things (not counting if I'm having a party)...well, It takes me 5-6 trips to the car to the house to unload it all. I don't see how this would be practical for living if you had to haul all this stuff back and forth between the grocery store, and the station, and from the station to the house. Hell, how would most people get their Xmas tree home from the tree lots to the house? It just doesn't seem practical for everyday life. If it was in addition to cars...well, sure that would work, but, if everyone could still have a car, and the independence it gives...well, that kills the personal transport thing too.

    Also, the thing that bothered me...CCTV's in every station/car? Just want we would need...another infringment on privacy, being filmed all the time...tracking your movements? Not for me thanks.

    And with weather....I see the examples of how a cold snowy climate like MN would have problems with a system like this...but, was thinking about New Orleans. Would be VERY difficult to evacuate with this system in such small cars. Even if it were nationwide and would get everyone out of the city..again, the smallness and lack of storage for traveling with personal property is an issue? How would you evacuate the city, and bring your pets?All your records you need...family pictures..etc. When you leave NOLA in fear of a hurricane...you bring all you can, 'cause there is that chance the city itself will be wiped off the face of the earth.Elderly people and their walker/wheelchairs...

    This also doesn't look practical for normal city emergencies. How would one of these function as an ambulance with all the equipment they need? Firetrucks? Police?

    It IS a neat idea..and possibly one that needs to be kept in the working on stage, but, it just does not seem at ALL practical for daily life as we know it. And these are just issues we have for more urban areas. A great deal of the US is not in the category...you'd still need roads out there to transport things....and if you have all these roads and vehicles still...what do you need the new 'transit' system for?

    Just some thoughts...

    --
    Light travels faster than sound. This is why some people appear bright until you hear them speak.........
  45. Re:Um, and so they should. The automobile is obsol by dangitman · · Score: 2, Insightful
    One malicious guy rejects every taxi then takes the last one. I suppose if they don't queue up like regular taxis that wouldn't be a problem.

    Then that malicious guy gets banned from the network, just like you would with a malicious user on your computer network. I just don't understand why people have to constantly think of any possible reason (no matter how trivial or stupid) to reject new technologies that might actually be more sustainable and efficient.

    I mean, big fucking deal. How does this inconvenience of "malicious users" in any way compare in scale or intensity to the problems of drunk drivers killing kids, air pollution giving us cancers and breathing problems, massive amounts of mining needed to produce the metal and oil to make enough private cars, traffic congestion, road rage, etc?

    It's not as if cars and subways don't both have massive problems. But no, let's not think of how to improve things. Lets just bitch about some new idea that might have some small potential problem.

    --
    ... and then they built the supercollider.
  46. Re:Um, and so they should. The automobile is obsol by Nefarious+Wheel · · Score: 2, Funny

    Living in Australia, we wouldn't have that problem. You see someone doing that, you walk up and whack 'em a good one on the ear hole. Problem solved.

    --
    Do not mock my vision of impractical footwear
  47. Re:New OS by KarmaMB84 · · Score: 2, Insightful

    Way to simplify Ethernet to the point of not even being Ethernet anymore. Ethernet is more than just the physical link.

  48. Re:Plan 9 by jericho4.0 · · Score: 2, Interesting
    From the Plan9 FAQ;

    "all the system objects present themselves as named files that are manipulated by read/write operations; second, all these files may exist either locally or remotely, and respond to a standard protocol; third, the file system name space - the set of objects visible to a program - is dynamically and individually adjustable for each of the programs running on a particular machine."

    The result of this is that each app or user session can run on a metacomputer. A CPU here, a CPU there, some storage over there and a display and mouse and keyboard here. SMP is automatic, your filesystem contains the entire internet (like you ask for), and "my computer" becomes a text file describing the resources you have acces to. Got a job you don't want to stop, but want to turn off the CPU by your bed?

    mv /proc/job /mynetwork/livingroom/proc

    (I'm making that up, but that's the idea...)

    --
    "A language that doesn't affect the way you think about programming, is not worth knowing" - Alan Perlis