Slashdot Mirror


Ask Unix Co-Creator Rob Pike

Today we return to our Slashdot interview roots with a "Call for questions" for Rob "Commander" Pike, who has been involved in the development of many modern programming concepts, GUI advances, character sets, and operating systems. We'll email 10 - 12 of the highest-moderated questions to Rob and post his answers as soon as he gets them back to us.

69 of 479 comments (clear)

  1. Plan9 by mirko · · Score: 5, Interesting

    Plan 9 was supposed to go even further than Unix went, does it really looks like to you that it's been conceived according to a similar approach ???

    --
    Trolling using another account since 2005.
    1. Re:Plan9 by Spyffe · · Score: 5, Interesting
      Rob,

      Right now, there are a large number of research kernels. Plan 9, Inferno, AtheOS, Syllable, K42, Mach, L4, etc. all have their own ideas about the future of the kernel. But they all end up implementing a POSIX interface because the UNIX userland is the default.

      The kernel space needs to be invigorated using a new userland that demands new and innovative functionality from the underlying system. Suppose you were to design a user environment for the next 30 years. What would the central abstractions be? What sort of applications would it support?

      --
      Sigmentation fault - core dumped
  2. Biggest problem with Unix by akaina · · Score: 5, Interesting

    Recently on the Google Labs Aptitude Test there was a question: "What's broken with Unix? How would you fix it?"

    What would you have put?

    --
    Remembering that you are going to die is the best way I know to avoid the trap of thinking you have something to lose.
    1. Re:Biggest problem with Unix by Anonymous Coward · · Score: 5, Funny

      If you know what's wrong and know how to fix it, why don't you fix it already! The source is out there.

    2. Re:Biggest problem with Unix by hackstraw · · Score: 3, Interesting

      Recently on the Google Labs Aptitude Test there was a question: "What's broken with Unix? How would you fix it?"

      I saw this google labs apt question, and while I've become numb to most of UNIX's issues and cannot think of a generic across the board (ie, cross vendor) "broken" thing except why the hell is UNIX so picky about 1) unmounting filesystems "that are in use" and 2) why the hell there is a 'D' run state that is completely uninterruptable?* The 2nd one really baffles me, and the first is just annoying, and fuser or some vendor specific tool can (sometimes) point you to the offending process that is using the filesystem. I found out today that fuser does not work on linux with the kernel NFS daemon sharing a filesystem and I try to unmount it. Annoying, but not as fundamentally broken as #2 in my opinion.

      Another thing that I see as "broken" in UNIX is that there is no normal/standardized/sane way of installing software. Debian gets it the closest, but the LSB picked RPM for some insane reason for package mismanagement on Linux.

      * For those that don't know, if there is something wrong with a disk subsystem, and a process tries to access that disk subsystem, the process is in an uninterruptable "disk wait state", that cannot be corrected without rebooting the computer. One can ususally safely ignore the processes stuck in this state, but its kinda irritating because it can often bring the system load up by one for each stuck process, yet it does not appear to hurt performance any.

    3. Re:Biggest problem with Unix by CondeZer0 · · Score: 3, Informative

      I think that he and the Bell Labs folks already answered those questions over 10 years ago:

      http://plan9.bell-labs.com/sys/doc/9.html
      (See specially the first section: Motivation)

      uriel

      --
      "When in doubt, use brute force." Ken Thompson
    4. Re:Biggest problem with Unix by mikefe · · Score: 3, Informative

      Actually, the refuse to umount if there are users in the mount is part of the POSIX or SUS specifications.

      Linux does not have a problem with it. That's why it has the -l option.

      -l Lazy unmount. Detach the filesystem from the filesystem hierarchy now, and cleanup all references to the filesystem as soon as it is not busy anymore. (Requires kernel 2.4.11 or later.)

      --
      There: Something at a specific location.
      Their: Owned by someone.
      Please make sure your english compiles.
  3. OK, here's the obligatory by w.p.richardson · · Score: 3, Interesting

    Looking back, what would you have done differently? Anything?

    --

    Curb CO2 emissions: Kill yourself today!

  4. resolv.conf by Flashbck · · Score: 5, Interesting

    why was the 'e' ever removed from resolv.conf?!!?!?

    1. Re:resolv.conf by JUSTONEMORELATTE · · Score: 4, Funny

      Ahh, you see, UNIX was created back in the day when we couldn't afford vowels, and many consonants.
      As such, common commands had to be shortened a little bit:
      "Copy" becomes "cp"
      "List" becomes "ls"
      "Rename" becomes "mv" and so on.

    2. Re:resolv.conf by roalt · · Score: 4, Funny
      Why was the 'e' ever removed from resolv.conf?!!?!?

      That was bcaus the -ky on my kyboard was not working as it should in thos days.

    3. Re:resolv.conf by orangesquid · · Score: 4, Interesting

      Short commands are easier to type, especially on slow TTL hardware where several context switches have to happen for every single keystroke.

      Early unix also had a 12-letter filename limit.
      I don't know if that included the NUL or not; if it did, then resolv.conf makes sense, since you might want to make a backup copy named resolv.conf~ or such. Also, early fortran had a 6-letter symbol name limit; this might be the reason for creat (so _CREAT would fit within the maximum 6 letters?)

      DISCLAIMED: Just some ideas, dunno if any of this is correct!

      --
      --TheOrangeSquid Is it any wonder things seem so awry? We swim in a sea of confusion and don't have to think to survive
    4. Re:resolv.conf by telstar · · Score: 4, Funny
      "Ahh, you see, UNIX was created back in the day when we couldn't afford vowels, and many consonants.
      • I blame that bitch Vanna...
    5. Re:resolv.conf by asdfghjklqwertyuiop · · Score: 3, Funny

      resolv.conf is exactly 11 chars


      exactly 11 characters? As opposed to filenames 11.0001 characters long?

  5. Apple and Unix by Anonymous Coward · · Score: 4, Interesting

    What are your thoughts on Apple's use of Unix.

  6. Re:What do you think of the SCO vs IBM? by stecoop · · Score: 5, Interesting

    Add to the question about what he thinks of the government forcing Bell to sell of the Unix OS (because the parent company was considered a monopoly) inlight of today's litigation wrangling.

  7. The future? by xenostar · · Score: 4, Interesting

    What do you see in the far future of operating systems, now that great advances in the way we think about computers, such as quantum computing, have been made.

  8. Is Linux "unix"? by Doc+Ruby · · Score: 4, Interesting

    Is Linux "unix"? What did Unix get wrong, but was too late to change by the time that you realized it, that Linux can still get right, while it's still young?

    --

    --
    make install -not war

  9. Are you suprised at the longevity of Unix? by sgant · · Score: 3, Interesting

    When you were creating it, did you in your wildest dreams ever think that 30 years people would still be using it on a daily basis? Was it designed from the beginning to grow and be added onto?

    --

    "Leo Fender was in a 'state of grace' when he designed the Stratocaster." -- Paul Reed Smith
  10. Languages by btlzu2 · · Score: 5, Interesting

    Hello!

    Maybe this is an overly-asked question, but I still often ponder it. Does object-oriented design negate or diminish the future prospects of Unix's continuing popularity?

    I've developed in C (which I still love), but lately, I've been doing a lot of purely object-oriented development in Java. Using things like delegation and reusable classes have made life so much easier in many respects. Since the *nixes are so dependent upon C, I was wondering what future you see in C combined with Unix. Like I said, I love C and still enjoy developing in Unix, but there has to be a point where you build on your progress and the object-oriented languages, in my opinion, seem to be doing that.

    Thank you for all your contributions!!!

    --
    Zed's dead baby. Zed's dead.
  11. Obvious (and probably redundant) by Camel+Pilot · · Score: 3, Interesting

    What do you think of the Evil called SCO?

  12. View on linux by noselasd · · Score: 4, Interesting

    What are your views on the free/OpenSource Unix like operating systems, such as Linux and the *BSDs ?

  13. Language for new OS's by Anonymous Coward · · Score: 5, Interesting

    The C programming language was written for and spread by the Unix operating system. While it's still a useful tool, and far better than the wholly untyped BCPL that preceded it, C is really starting to show its age. Is there an existing programming language that you would recommend for the implementation of operating systems? Would you recommend creating a new language for a new OS, as was done with Unix? Would you recommend the creation of new OS's at all?

  14. Innovation and patents by Zocalo · · Score: 4, Insightful

    With so many of your ideas being used with such ubiquity in modern operating systems, what is your stance on the issue of patenting of software and other "intellectual property" concepts? Assuming that business isn't going to let IP patents go away as they strive to build patent stockpiles reminiscent of the nuclear arms buildup during the cold war, how would you like to see the issue resolved?

    --
    UNIX? They're not even circumcised! Savages!
  15. CLI by Moby+Cock · · Score: 5, Interesting

    Has the Command Line Interface become outdated? What are your thoughts on the CLI and if you had to 'do it all again' would the CLI be as prevalent?

    1. Re:CLI by Naikrovek · · Score: 3, Insightful

      The command line was the ONLY interface when unix was first developed. X came long after the CLI and even if you're running Windows you still use the command line from time to time. If you don't you're just not using the power of your system, in my opinion.

      raw text is the only true inter-system communication protocol. my cats and my computer understand a lot of the same words. my cat can't type but i can, and my computer can't understand the noises my cat makes, but i do - command pipes! where would we be without those, and those ONLY work in the CLI! we would be in the stone ages of computing without the CLI.

  16. Systems research by asyncster · · Score: 5, Interesting

    In your paper, systems software research is irrelevant, you claim that there is little room for innovation in systems programming, and that all energy is devoted to supporting existing standards. Do you still feel this way now that you're working at Google?

  17. the old school by Triumph+The+Insult+C · · Score: 4, Interesting

    what modern OS reminds you the most of your old school OS hacking days? what OS do you think keeps closes to the *nix spirit?

    --
    vodka, straight up, thank you!
  18. One tool for one job? by sczimme · · Score: 5, Interesting


    Given the nature of current operating systems and applications, do you think the idea of "one tool doing one job well" has been abandoned? If so, do you think a return to this model would help bring some innovation back to software development?

    (It's easier to toss a small, single-purpose app and start over than it is to toss a large, feature-laden app and start over.)

    --
    I want to drag this out as long as possible. Bring me my protractor.
  19. Back in The Day by Greyfox · · Score: 5, Interesting

    Were programmers treated as hot-pluggable resources as they are today? There seems to be a mystique to the programmer prior to about 1995. From reading the various netnews posts and recollections of older programmers, it seems like the programmer back then was viewed as something of a wizard without whom all the computers he was responsible for would immediately collapse. Has anything really changed or was it the same back then as it is now? I'm wondering how much of what I've read is simply nostalgia.

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  20. ReiserFS and the future of file systems by booch · · Score: 5, Insightful

    What do you think of the work Hans Reiser is doing with file systems? How does it differ from and/or improve upon Plan 9? What do you think of his theory that (nearly) all database functions should be done by the file system? What do you think about being able to treat files as directories in order to get to special (or not special) info? Is it useful to be able to treat a tarball as a file when you want to and as a directory when you want to? How about file metadata? Data forks? Do you think Linux, Windows, or Mac OS X will come up with the better database/search-enhanced file system?

    --
    Software sucks. Open Source sucks less.
  21. Since you now work for Google... by anonymous+cowherd+(m · · Score: 4, Interesting

    How can search as a concept become better integrated into the desktop? Are projects like dashboard the next killer app?

    --
    http://neokosmos.blogsome.com
  22. Is systems research really dead? by Xpilot · · Score: 5, Interesting

    After reading your presentation on the death of systems research, I was rather disappointed at the dismal situation presented. Has anything changed since you presented that talk, or have your thoughts changed about the matter? As someone who is interested in systems research, what do you think is the most promising direction that is emerging today?

    --
    "Backups are for wimps. Real men upload their data to an FTP site and have everyone else mirror it." -- Linus Torvalds
  23. Why did it take Linux to popularise Open Source? by RLiegh · · Score: 4, Interesting

    The GNU movement started on old Unix computers, and was aimed in part at them; so why do you think it is that the first wave of unix users were so resistent to the concept of Open Source?

  24. Plan 9/OS insights from Google? by jwjr · · Score: 5, Interesting

    Do you find any role for Plan9 at Google? Does Linux (or Linux with whatever customizations, extensions, and metamorphoses Google imposes on it) do everything Google needs or wants out of an OS platform? Does your experience with operating systems research pay off directly in contributing to the shape of the Google platform, whether for individual machine OS's, or for co-operation and clustered operation on the network?

  25. Driving force of OS' by cpfeifer · · Score: 4, Insightful

    What will drive the next crop of OS'? Is it in hardware innovations, new programming languages?

    --
    it's not going to stop until you wise up, no it's not going to stop. so just give up.
  26. He's NOT a Unix co-creator by hruntrung · · Score: 5, Informative

    Jeez, someone, click on the fuckin link in the post with his name. He's not a Unix co-creator. He worked a lot on Plan 9, and wrote a bitmap windowing system for Unix. But he's not a Unix co-creator. The creators of Unix are Dennis Ritchie and Ken Thompson.

    1. Re:He's NOT a Unix co-creator by sgant · · Score: 3, Insightful

      Ah, so maybe you should email Roblimo and tell him this since the whole story is:

      "Ask Unix Co-Creator Rob Pike"

      Set Roblimo straight then...instead of just spouting off in the forums where no one but me will see it.

      --

      "Leo Fender was in a 'state of grace' when he designed the Stratocaster." -- Paul Reed Smith
  27. Article theft by Zedrick · · Score: 5, Informative

    The operating systems link goes to encyclopedia.thefreedictionary.com, which is a scam-site that steals articles from other sites, in this case from Wikipedia. The only thing they've added are ads. The original can be found at http://en.wikipedia.org/wiki/Plan_9

  28. The future of *NIX by mbonig · · Score: 3, Interesting

    As *NIX and linux become increasingly popular in the business place people are looking to push Microsoft out of the field, replacing servers and workstations with free alternatives like Linux and some BSDs. This is causing kernels and OS designed for server performance to progress to desktop solutions. Do you feel that *NIX should stay in the server marketplace and focus solely on that market, or do you think moving the OS/kernel into a desktop role is "A Good Thing"??

  29. Xanadu, Google, & Plan9 by Anonymous Coward · · Score: 4, Interesting

    Computing has advanced so much in the past ten years that it seems it's impossible to go back and correct any origional mistakes in the way we think about computers. With the amount of money behind the corporate machine, it really seems as if incredible ideas like Plan 9 and Xanadu are now things of the past--once good ideas that could have changed the way we approach computing, that simply missed their time. Do you see hope for these ideas and projects, or any other new or old computing paradigms that have potential for big change, but would require scrapping, say, the past several years of stagnant and unorigional work? -Ryan

  30. Microkernel vs. Monolithic by Ransak · · Score: 5, Interesting

    In the marketplace, monolithic OSes seem to be dominating, despite the advantages of microkernel OS design. I know this is straying into many other issues but from your point of view, why are monolithic OSes still viable in the marketplace - and why hasn't the public (ie, the 'programming public') demanded more?

    --
    "Powers. I have them."
  31. What are you doing... by Mark+Wilkinson · · Score: 5, Interesting

    Google employees are apparently allowed to work on their own projects 20% of the time. Given that you probably can't comment on what you're doing for Google, what are you doing to fill the other 20%?

  32. The Year 2038 Bug by WormholeFiend · · Score: 3, Interesting

    End of the World, or not?

  33. The Google Operating System by andyfaeglasgow · · Score: 3, Interesting

    Can you comment on the speculation about a new Operating System being created by Google?

  34. Lack of variety in operating systems by Junks+Jerzey · · Score: 4, Interesting

    Most people graduating with computer science degrees are only familiar with Windows and a handful of UNIX-variants: Linux, BSD, OS X. Is it good that stable technology is becoming the standard, thus allowing developers to focus their attentions elsewhere, or was this tremendous reduction in variety premature?

  35. Revolution Needed? by Anonymous Coward · · Score: 5, Interesting

    When Unix came out, it was written in the highest level language of any operating system: C. Why do you feel that operating systems are still implemented using the oldest, lowest-level languages?

    With recent advances in high-level application languages like Java (low-latency garbage collection, dynamic inlining, etc), it seems to me that an operating system based on such a language would offer far more opportinuty for a vastly different kind of operating system more akin to an operating environment. Haven't attempts to add object-oriented features, such as in Plan 9 or to a limited extend Mach, failed due to the choice of implementation language?

    It's just painful to see all the disgusting machinations necessary to implement a filesystem, network stack, scheduler, etc in C/C++...

    1. Re:Revolution Needed? by Empty+Threats · · Score: 3, Insightful

      Correction, when UNIX "came out," it was written in the lowest level language of any operating system. Everything else was either written in straight assembly or a sane language, like Lisp or PL/I. Furthermore, Lisp had all those lovely features in 1975.

      It's also worth noting that many the problems we have today are based in the concept of the "operating environment" -- today's software and hardware design paradigms are rooted in C. Implementing any language other than Algol-derivatives on top of C certainly fits into the category of "disgusting machinations."

      In short, as people have recognized for twenty years or more, UNIX succeeded because it was the lowest common denominator, not because it was any good.

  36. Thoughts on Bell Labs. by geeber · · Score: 5, Interesting

    Plan 9, Unix and so many other great things came out of Bell Labs. Since the crash of the internet bubble, telecom companies have suffered immensely. One of the results of this is that Lucent has systematically dismantled one of the worlds greatest industrial research facilities. You spent a great part of your career at Bell Labs. What are your thoughts about the history and future (if any) of Bell Labs, and how did the culture of the Labs influence the growth of Unix?

  37. probably redundant by this point... by Guano_Jim · · Score: 5, Funny

    emacs or vi?

  38. Silver medal in Archery at the 1980 olympics? by Anonymous Coward · · Score: 5, Interesting

    Your bio at bell labs and most other bios writen about you, mention that you won the silver medal in archery at the 1980 Olympics.

    First, the US and Canada boycotted those olympics.
    Second, Boris Isachenko, URS(BLR) won the silver medal at those olympics.

    Is this an example of a joke that now has become folklore? Is it a way to "prove" to people that they should check their sources? Or is it just puffing up one's resume?

    It seems strange in an era of quick and dirty research that you would still post this on your bio at bell labs. It only took a quick "I'm feeling lucky" google search on "1980 Olympics archery" to pull that info up.

    So my question is, why do you keep that on your bio?

  39. Bitterness about Linux from older developers by Junks+Jerzey · · Score: 5, Interesting

    Among a certain crowd, Linux is viewed at the savior of computing--a young, hip operating system for the new century. But at the same time, there have been definite twinges of bitterness from a more old-school crowd, including people like Brian Kernighan, Jaron Lanier, and possibly even you. This bitterness appears to stem from the horror of a 25 year old operating system returning to the forefront of computing (for anyone vehemently disagreeing, consider if clones of VMS or OS/360 were suddenly all the rage). Who is right? What's your take?

  40. An old grudge, an new liscense? by emil · · Score: 3, Interesting

    Two questions:

    1. Dave Cutler, mastermind of the Windows NT kernel, once described UNIX as a "junk OS designed by a committee of Ph.D.s.".

      Given two important facts:

      • Windows NT is mostly written in C and C++, both Bell Labs innovations, and
      • IE/Mediaplayer integration has turned the Windows NT codebase into a security disaster

      How would you respond to Cutler's assertions, and how would you rate the code quality of the NT kernel (assuming that you might have perused the recent leaked NT4 source)?

    2. While UNIX-like operating systems are growing in popularity, actual Bell Labs code is rarely encountered in free operating systems because of licensing issues (with a few notible exceptions).

      This is a frustrating situation for all of us. Do you see any possibility that major portions of UNIX and Plan 9 source being released under licensing that major distributions would find acceptable?

    Please also accept my personal thanks for your work in the field of computer science. The influence of the community of researchers at Bell Labs will be felt for many generations to come.

  41. starting from scratch today? by Nerkles · · Score: 3, Interesting

    If you were just starting out with today's computers, what would you do differently or the same?

  42. Freeness by identity0 · · Score: 4, Insightful

    How much do you think UNIX's success has been shaped by the relatively light restrictions placed on its use, distribution and modification?

    The original UNIX, BSD, and now Linux seem to have been 'freeer' than other OSes of the time, do you think they would have been successful without this?

    Finally... vi or Emacs? ; )

    1. Re:Freeness by identity0 · · Score: 4, Interesting

      Oh, and an addendum - Do you think Plan 9, or any other OS with a relatively restrictive license can succeed now against traditional UNIXes and Microsoft?

  43. Hardware by SwansonMarpalum · · Score: 5, Interesting

    Rob, When you were engineering UNIX, processors weren't as beefy, memory was grotesquely expensive, and storage was a premium. These days all of these resources have largely become commodities and can be frittered away wastefully by neglectful programmers. Do you think that in an alternate world where UNIX hadn't been conceived as early in the progression of hardware as 1970, rather had come along at this stage in the timeline where hardware vastly outpaces all but the most glaringly negligent software, it would have been as compact, fast and efficient? Thanks! -Alex R.

    --
    "Give away the stone, let the oceans take and transmutate this cold and faded anchor." - Maynard James Keenan
  44. More obligatory questions by sleepingsquirrel · · Score: 5, Interesting

    What operating system to you use the most for your personal and/or work-related needs?

  45. HURD by Anonymous Coward · · Score: 3, Interesting

    Someone please put together a good question about The HURD and his views on the project, if I do it, it won't get modded up, I'm bad at expressing myself in english.

  46. Plan9 advantages over Linux and *BSD by Florian · · Score: 5, Interesting

    In which areas would you say is Plan9 (still) ahead of Linux/GNU and *BSD, the two operating systems which represent the most contemporary iteration of the original Unix design?

    --
    gopher://cramer.plaintext.cc http://cramer.plaintext.cc:70
  47. Would you consider Mac OS X a version of Unix? by the_webmaestro · · Score: 5, Interesting

    What do you think of Mac OS X? Have you used it? Would you consider Mac OS X a 'version' of Unix? Would you consider using it as your main operating system? What do you loave about it? What do you hate about it?

  48. Schemas for UNIX by generalphilips · · Score: 5, Interesting

    Unix suffers today from a proliferation of file and output formats that makes integration between the CLI/config files and the GUI awkward at best. For example, a common idiom for Unix GUI tools is to parse output from a CLI program and present it visually. This would be greatly simplified and much smoother if those programs produced structured output rather than raw text. The same holds for programs that read configuration files, like resolv.conf. Do you think UNIX would benefit from standardization of formats that coalesce around XML? What do you think of the idea of developing schemas for OS objects? What about schemas for common application-level objects - the idea behind WinFS?

    I realize the question needs work, but I hope you get the idea.

  49. Power by schon · · Score: 4, Insightful

    True. CLI is the equivalent of spoken or written language, and the GUI is the equivalent of pointing at something and grunting.

    Spoken/written communication is much more powerful (easier, faster, more effective) when both parties understand the language, and the idea is a complex one ("I would like a job at your pie shop.")

    Rudimentary communication is easier with point-and-grunt (answering the question "which pie would you like to purchase?" - you point to the one you want)

    If the parties don't understand the same language, complex concepts are *much* harder. Learning to communicate by pointing is easier, but the true power of communication comes from spoken/written languages.

    Think I'm wrong? Write a detailed response *without* using your keyboard.

  50. Intellectual Property by lordvdr · · Score: 3, Interesting

    The US (and to some extent, the EU) are facing mounting issues from Software Patents (The idea of patenting an idea opposed to an implementation). What do you think about the current state of Intellectual Property laws?

    What limits should be placed on Software Patents? Should they be eliminated entirely? Should all patents be moved to a trademark like system where if they are not enforced, the holder loses the trademark?

    What is the fix and what is needed to make it happen? Will it ever be fixed?

    --
    If you are out to describe the truth, leave elegance to the tailor - Albert Einstein
  51. If you could write a new OS from scratch by LWATCDR · · Score: 4, Interesting

    What would it be like. Would it still be unix like?
    What would you write it in? I mean if you had the time, money , and a mandate to create the best OS ever and you did not have to care about backward compatability what would you come up with.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  52. Your Biggest Mistake we're still suffering from? by bsdnazz · · Score: 3, Interesting

    What's the biggest mistake (design, paradigm, API) you've made that we're still suffering from. And I don't mean leaving the e off creat()!

  53. X11 in the future by moath · · Score: 4, Interesting

    Do you see X-Windows (in whatever form) as a viable platform for GUI technologies in the future or is it approaching the point of diminishing returns?

  54. Language based operating systems by stevedekorte · · Score: 5, Interesting

    Do you see a future for language-based operating systems like the old Smalltalk and LISP machines or the Newton?

  55. Database filesystems by defile · · Score: 4, Interesting

    The buzz around filesystems research nowadays is making the UNIX filesystem more database-ish. The buzz around database research nowadays is making the relational database more OOP-ish.

    This research to me sounds like the original designers growing tired of the limitations of their "creations" now that they're commodities and going back to the drawing board to "do things right this time". I predict the reinvented versions will never catch on because they'll be too complex and inaccessible.

    Of course, this second system syndrome isn't just limited to systems. It happens to bands, directors, probably in every creative art.

    I think what we've got in the modern filesystem and RDBMS is about as good as it gets and we should move on. What do you think?