Live data from Hacker News

Operating Systems: From 0 to 1

tuhdo.github.io

71–80 of 82 posts

Re: Operating Systems: From 0 to 1

#71

It's a from-first-principles guide to building an OS. From the title, I had mistakenly assumed it was about the first OS ever.

Like almost everything in Computer science there would be no clear definition of first OS ever. There used to be monitor programs and schedulers before they iteratively evolved into OS programs. Just like, programming languages, servers, 'cloud'... There seldom is a first ever something in our field.

Im curious what "monitor programs" means here in this context?

The first OS was OS/360 at IBM in 1964.

Re: Operating Systems: From 0 to 1

#72

Earlier quoted context omitted.

Like almost everything in Computer science there would be no clear definition of first OS ever. There used to be monitor programs and schedulers before they iteratively evolved into OS programs. Just like, programming languages, servers, 'cloud'... There seldom is a first ever something in our field.

Im curious what "monitor programs" means here in this context? The first OS was OS/360 at IBM in 1964.

OS/360 was not the first OS. Quite a number of operating systems came before it.

Examples of earlier operating systems include SHARE Operating System (SOS), first version in 1959, for the IBM 709 mainframe; which in turn was itself was based on an earlier operating system, GM-NAA I/O, first version in 1956.

A very notable pre-OS/360 operating system was MIT's CTSS operating system, the first timesharing OS, first version in 1961 for the IBM 7094. The first versions of OS/360, by contrast, notably lacked timesharing – that was initially provided by alternative IBM operating systems (TSS/360 was the official answer and CP/CMS, which later became VM/CMS, the principal unofficial one); OS/360 only gained timesharing support itself when TSO was released in 1971.

Re: Operating Systems: From 0 to 1

#73

Earlier quoted context omitted.

Can you explain more what inspired you in this sentence or are you still thinking it's bizarre? And if you do still think it's bizarre why would that convince you to donate?

not OP, but one thing we as developers should recognize is that programming itself is likely to become merely a skill like operating a spreadsheet or typing. In much the same way, writing was once a skill available (or at least, practiced) by a very small subset of people, and the spread of literacy made the job of "scribe" largely irrelevant over time. Children today are learning how to program—perhaps not yet in th…

Interesting...... What will they do in the future? Because by then bank jobs would be gone, basic health care would be performed by robots, and even writing by machines. Hell, everyone would be at home .

Re: Operating Systems: From 0 to 1

#74

Earlier quoted context omitted.

Can you explain more what inspired you in this sentence or are you still thinking it's bizarre? And if you do still think it's bizarre why would that convince you to donate?

not OP, but one thing we as developers should recognize is that programming itself is likely to become merely a skill like operating a spreadsheet or typing. In much the same way, writing was once a skill available (or at least, practiced) by a very small subset of people, and the spread of literacy made the job of "scribe" largely irrelevant over time. Children today are learning how to program—perhaps not yet in th…

We still have a lot of different kinds of scribes.

The number of people who can put together effective, performant and reasonably correct systems is not that large.

Re: Operating Systems: From 0 to 1

#76
post #68

Every time an OS book (about weekly) is posted on HN, I immediately want to jump all over it but I gently remind myself to finish: CMU's Computer System's from a programmer's perspective and Elements of computing (nand2tetris).

It seems you've already decided that these are worth reading, but in case you want some motivation, I had CS:APP as my textbook last term and I thought it was quite nice. I also worked through TECS several years ago and it was also a great resource. CS:APP is quite dry but by the end of the course I was able to write a real memory manager in C, which was super fun! If you're ever looking for an internet book reading…

TECS? I would like to have online buddy to do this self-learning courses. Most of my projects fizzled due to lack of accountability.

Re: Operating Systems: From 0 to 1

#78

Earlier quoted context omitted.

Like almost everything in Computer science there would be no clear definition of first OS ever. There used to be monitor programs and schedulers before they iteratively evolved into OS programs. Just like, programming languages, servers, 'cloud'... There seldom is a first ever something in our field.

Im curious what "monitor programs" means here in this context? The first OS was OS/360 at IBM in 1964.

https://en.m.wikipedia.org/wiki/Resident_monitor

Re: Operating Systems: From 0 to 1

#79
post #68

Earlier quoted context omitted.

It seems you've already decided that these are worth reading, but in case you want some motivation, I had CS:APP as my textbook last term and I thought it was quite nice. I also worked through TECS several years ago and it was also a great resource. CS:APP is quite dry but by the end of the course I was able to write a real memory manager in C, which was super fun! If you're ever looking for an internet book reading…

TECS? I would like to have online buddy to do this self-learning courses. Most of my projects fizzled due to lack of accountability.

TECS is The Elements of Computing System. Feel free to send me an email!

Re: Operating Systems: From 0 to 1

#80
post #15

From the book: "If a programmer writes software for a living, he should better be specialized in one or two problem domains outside of software if he does not want his job taken by domain experts who learn programming in their spare time." Seems a bizarre sentiment, but after reading this sentence, I feel like I really wanna donate some money to the guy. If he gives a way I will surely do.

Can you explain more what inspired you in this sentence or are you still thinking it's bizarre? And if you do still think it's bizarre why would that convince you to donate?

I was misunderstood. What I find bizarre is my felling to want to give money for the reason that that phrase resonated with me a lot. The sentence he wrote is not bizarre at all. It is a gem.
Post reply on HN