Skip to content
HomeVideosBooksBlogs
AllTop postsTopics
Podcasts
HistoryListsWatch laterLiked videosFollowing

The videos, books, blogs and podcasts Hacker News keeps recommending, all in one place.

VideosBooksBlogsPodcastsAboutPrivacySettings

Data from Hacker News, HackerTube, HackerBooks, HackerBlogs and Open Library. Credits · Not affiliated with Y Combinator.

HomeVideosBooksBlogsPodcasts
Ctrl K
    R

    Rob Pike

    herpolhode.com · Personal blog · on HN since 2008

    Rob Pike, a Bell Labs and Go veteran, hosts talks and papers on operating systems, Plan 9, Inferno, and Unix.

    Visit blogHN submissions
    Systems & PerformanceOpen Source & LinuxHistory
    What HN says

    HN links it mainly for his "Systems Software Research is Irrelevant" talk, which commenters cite as still relevant about stagnation in operating systems.

    Stats for nerds
    53HN people shared it
    27linked in comments
    458story points
    Jun 2026last shared
    2010people per year2026

    Top posts on HN

    1. 1
      Systems Software Research is Irrelevant (2000) [pdf]
      37 people · 182 points · first shared 2010 · 68 comments on HN
    2. 2
      An Introduction to Quantum Computation and Quantum Communication (2000) [pdf]
      2 people · 129 points · first shared 2011 · 8 comments on HN
    3. 3
      Rob Pike (2001): Presentation looking back on 1 billion seconds of Unix. [pdf]
      9 people · 128 points · first shared 2008 · 32 comments on HN
    4. 4
      Rio: Design of a Concurrent Window System (2000) [pdf]
      1 person · 13 points · first shared 2015 · Discussion on HN
    5. 5
      Design of the Inferno Virtual Machine
      1 person · 5 points · first shared 2020 · Discussion on HN
    6. 6
      Systems Software Research is Irrelevant (Rob Pike, 2000)
      1 person · 1 points · first shared 2014 · Discussion on HN
    7. 7
      Xray
      1 person · first shared 2026
    8. 8
      Rob
      1 person · first shared 2020

    What HN people wrote when they linked it

    • bcaa7f3a8bbcSep 2018

      >The future is already here — it's just not very evenly distributed.

      Nobody is denying it, indeed we see many related development.

      However, it's not only about "the lost future that never comes", I think it's also due to the people being increasingly alienated about the current state of computing. Primarily, it's about the lost mentality of the future.

      Cyberpunk promised a future where computing is the disruptive technology. Since 2006, the ever-increasing clock speed came to a halt. Since 2013, the general performance of Intel processors remained constant. Selling of PCs keeps declining. No major breakthrough in practical operating systems are made beyond Unix (http://herpolhode.com/rob/utah2000.pdf).

      Cyberpunk promised a future where megacorps and governments being increasingly oppressive to the population with technology, it has occurred as predicted. Cyberpunk also promised the "cyberspace" is going to be the electronic frontier where technologists reclaimed liberty... Today, the damn web browser that runs all the craps written in Electron and JavaScript is hardly the "frontier", neither Facebook, Twitter and the endless timeline of buzz, which constitute 90% of the Internet activities count. Also, from 2000-2013, decentralization was killed, not built. Move importantly, today, we don’t even know how to waste time on the Internet anymore (https://news.ycombinator.com/item?id=17068138). Though, It, still, has arguably occurred to some extents too, but progressed…

    • dashtSep 2010

      (In my opinion) Here's a bunch of reasons why Plan9 isn't popular, and then a reason or two why something like it likely will be before too long:

      The first obvious answer (also mentioned in other comments) is because "Systems Software Research is Irrelevant". See Rob Pike's paper by that name: http://herpolhode.com/rob/utah2000.pdf

      To the reasons Pike offers there, I'll add:

      1. The companies that owned the software had poor strategies for encouraging widespread adoption, if that was even ever their goal.

      2. The first dot-com boom ca 2000 greatly expanded the IT / programmer workforce and (I claim) significantly dumbed it down. The advantages of a new operating system lack economic impact until a huge number of programmers are trained to use those advantages. We have huge sunk costs invested in maintaining a huge supply of mostly weakly skilled programmers and admins, a sort unlikely to adapt to and adopt a new OS.

      3. In a related way, the sectors that could in principle drive something like Plan 9 adoption are heavily invested, by now, in massive amounts of bloatware that, dysfunctional as it is, is both critical and non-portable.

      4. Modern hardware is fast enough that fairly high level programming languages and environments tend to dominate. These often include a "least common denominator" view OS capabilities so that programs port easily among Windows, Linux, Unix, MacOS, etc. This hurts demand for OS features other than the "least common…

    • vilhelm_sAug 2014

      I do think there is a big difference in academic computer science now and then. Rob Pike has written about it from an operating systems perspective [1], and Richard Gabriel from a programming language perspective [2]. It seems that until the early 1990s, there were lots of projects focused on building "systems", i.e. big pieces of software which are in themselves practically useful; then there is a sharp shift and academic research focus on "theory" (in PL research, e.g. a type safety proof for small core calculi, or a particular algorithm for program analysis).

      People have always pursued "small" ideas. But I think the fact that we stopped writing "big" systems is a real change. (I guess the reason is that off-the-shelf operating systems and programming languages gradually got better, until it became impossible to "compete" with them. C.f. the Lua langauge, which got written basically because "western" langauges were not easily available at the time). My impression is that there is a lot less diversity of ideas now than there used to be, because everyone is incrementally improving the same set of OSs/langauges.

      [1] http://herpolhode.com/rob/utah2000.pdf
      [2] https://www.dreamsongs.com/Files/Incommensurability.pdf (see the section starting on page 10)

    • panicJan 2018

      > The success of browsers is an indictment of the entire field of operating systems research.

      Rob Pike wrote in the year 2000 that systems software research was irrelevant (http://herpolhode.com/rob/utah2000.pdf), and it seems to me that not much has changed since then. How many ideas from the last few decades of operating systems research have actually been put into practice?

      The real problem is more fundamental: people want their software to keep working. As Rob Pike put it in the talk linked above, "to be a viable computer system, one must honor a huge list of large, and often changing, standards: TCP/IP, HTTP, HTML, XML, CORBA, Unicode, POSIX, NFS, SMB, MIME, POP, IMAP, X, ... With so much externally imposed structure, there’s little slop left for novelty."

      For example, I'm sure some software out there is using the OpenGL API in a fundamentally insecure way. Changing the API to be safe would break this software. And maybe that would be a good tradeoff, if reworking OpenGL were the only thing you needed to do to safely run untrusted code. But almost every part of the system would have to change. You'd be left with a system which breaks or degrades pretty much everything you try to run on it.

    • patternsNov 2020

      This reminds of Robert Pike's "Systems Research is Irrelevant" speech [1]. Now, 20 years after his speech, we are still stuck with the same notions (such as everything being a string). It's not that there are not plenty of alternatives around, however, expectations are so high that it's almost impossible to make a new computer system economically viable. On the other hand, the hacker and maker scene is very active, some of them building operating systems and hardware such as tiny Lisp-based machines [2] and OSes [3]. (My only gripe is that most of the new "avant-garde" systems are still text/file-based.)

      I'd love to see a next wave in personal computing, starting with a clean slate, building on the research, insights and learning from the mistakes that have been made. I have no doubt that it will happen, the question is only when.

      As for interoperability: Even on the same platform there are countless problems getting software to talk to each other, so I don't think that a new system will make the situation any worse.

      [1] http://www.herpolhode.com/rob/utah2000.pdf

      [2] https://www.tindie.com/products/lutherjohnson/makerlisp-ez80-lisp-cpm-computer/

      [3] https://mezzanos.herokuapp.com/

    • wolfgkeSep 2014

      What Rob Pike is refering to is of course Plan 9 and its derivatives (say Inferno). Whether you want to consider them Unix-likes or not is your choice (many HNers will say it's more Unix than Unix).

      If you look for desktop alternatives to Unix, OSes to look at are BeOS (an open source clone is developed under the name HaikuOS) and the Windows NT kernel (don't hurt me: the Windows NT kernel is IMHO far more elegant than, say Linux or Mach. What is crappy is especially the WinAPI; please look deep below the surface: Here Windows gets nice).

      The reason why you won't find many desktop/server alternatives to Unix can be read here: http://herpolhode.com/rob/utah2000.pdf
      Thus lots of OS reserach is either focused on embedded stuff or virtualization instead of desktop or server.

      Accepting this, especially have a look at the L4 kernel family (a family of very small and fast microkernels). If you like highly secure designs, you'll probably like seL4, the first formally verfied kernel. Also QNX is worth a look (QNX is Unix, accepted; nevertheless a very elegant kernel design).

    Related

    Aphyraphyr.com551 people

    Hexing the technical interview (2017)

    Aphyr
    Personal · last shared 2026
    Brave New Geekbravenewgeek.com85 people

    You Are Not Paid to Write Code

    Brave New Geek
    Personal · last shared 2026
    The Morning Paperblog.acolyer.org606 people

    Local-first software: you own your data, in spite of the cloud

    The Morning Paper
    Personal · last shared 2026
    Astral Codex Tenastralcodexten.substack.com845 people

    Heuristics that almost always work

    Astral Codex Ten
    Personal · last shared 2026
    Chris Siebenmannutcc.utoronto.ca/~cks388 people

    Go is Google's language, not ours

    Chris Siebenmann
    Personal · last shared 2026
    John Ousterhoutstanford.edu/~ouster17 people

    John Ousterhout on Startup Decision-Making

    John Ousterhout
    Personal · last shared 2014
    Interconnectsinterconnects.ai74 people

    A look at Apple's technical approach to AI including core model performance etc.

    Interconnects
    Personal · last shared 2026
    Bluish Coderbluishcoder.co.nz77 people

    Using Freenet

    Bluish Coder
    Personal · last shared 2025