1. 39
  1.  

  2. 12

    Of all the horrible things, this is the worst of them:

    I was not allowed to rent books that were not strictly relevant to school work and this made the 6 hours after school incredibly slow

    In all seriousness, this is terrible on so many levels.

    1. 2

      I told my wife about this and this is what I read from her facial reaction. Her eyes widened, her jaw dropped. I had the same reaction, it IS quite terrible.

      1. 1

        If i were him, I’d try to strike a deal with his English teacher, asking him to provide false assignments, so he can read more stuff. Or just outright stay in school longer.

    2. 3

      This is super sweet. I’m really looking forward to seeing the code.

      Some people have claimed he only wrote a DOS shell. It’s true that he wrote a DOS shell, but it sounds like he also ran it on a clone of MS-DOS that he also wrote. So this is legit. Edit: no, wait, he meant he wrote a clone of MS-DOS COMMAND.COM in QBASIC.

      Discussion elsewhere: PC gaming subreddit (234 comments), Australia subreddit (150 comments), Geek subreddit (34 comments), osdev subreddit (5 comments), cyberpunk subreddit (59 comments), HN (208 comments).

      1. 2

        What is an Operating System though, really, anyway? I mean, Microsoft have gotten away with “a new shell on DOS” for a few iterations of their product, and ultimately .. to the Consumer .. the line is irrelevant. To a developer, we can move the line in the sand all over the tarpit, but the answer is never so black and white as to what constitutes an Operating System versus what is just a set of loosely-couple applications sharing a common core, integrated in some manner.

        To the user the question of “OS” versus “App” is .. fundamentally .. totally irrelevant.

        To the developer, its as simple as this: whatever the User first boots when they turn on the machine, is the Operating System. Whatever they do with it repetitively, is their Application.

        I think he built a set of both, and its a genius and beautiful, if a little sad, story. Haven’t we all felt compelled to push the limit in the face of oppression? This is an expression of that.

        1. 2

          An operating system is the system that

          • loads one program after another and sets up the I/O devices for each of them, and optionally
          • context-switches between them to hide I/O latency and virtualizes disk and RAM so they don’t stomp on each other, and
          • maybe keeps accounting records so you can bill users for CPU time,

          so that

          • you don’t have to hire a computer operator to do setup and teardown for each job and load each new card deck by hand, and so that
          • you don’t have expensive downtime during manual setup and teardown.

          That’s why it’s called an operating system: it’s a (software) system that automates away the computer operator’s job of operating the computer, by loading jobs into it and arbitrating between the jobs' conflicting demands on computer resources.

          Thus ends today’s history lesson.

          And yeah, there’s a lot of flexibility to move functionality between the operating system and the programs it runs. But I’d say that at a minimum an “operating system” has to load more than one other program into memory and run them.

          I agree about the genius, beautiful, sad part. He could have done so much more if only he’d known…

          1. 1

            I like to think of an OS as a computer designed to be shared among programs (where ‘computer’ includes virtual machines broadly defined). It’s not exactly the historical meaning – I actually wanted to sort of jettison some of the history.