Re:Ask HN: Would self-taught programmers be interested in su...
by sosagain on Wednesday May 07, 2014 @04:03PM
(#7712341)
For a mature programmer like you, it probably feels redundant to write a book that iterates concepts you have understood long ago. This book is for beginners. I have notice that many students graduate from University without actually understanding the concepts completely. It's a book I wish had existed when I was an undergraduate student.
Re:Ask HN: Would self-taught programmers be interested in su...
by brudgers on Wednesday May 07, 2014 @04:44PM
(#7712549)
Though mature, I'm well within the criteria you describe. Perhaps that's why I am a little familiar with what is already available for beginners. The issue for undergrads isn't that resources don't exist, it's that they don't know what exists. Twenty years ago my CS major neighbor turned me on to Mosaic, but had never heard of Dr. Dobbs. And he was a senior. A year ago, I was talking with a CS Junior who knew nothing about what an embedded system was. He only became aware at a job fair. Hadnt heard of YC either, sohe got my copy of Hackers and Painters.
Anyway, the danger you face is that you've cut the scope all the way back to undergraduates and begun to cast it as a traditional textbook. One that has to introduce C and x86 assembly and has to address the practical issues of testing and running a new minimal OS on their development machine [under Windows, OSX, and Linux?]. How much of what you want to write gets left out and how much of what you do write winds up being superficial instead of what you wish you had known?
Operating Systems: Three Easy Pieces [1] covers the really interesting parts of the book you are considering, and skips the parts that can't really be given decent treatment: x86 Assembly, C, and writing a toy operating system. Likewise, Linux from Scratch covers understanding the practical side of Operating Systems [2].
A book I want to read has "EMACS really is an operating system" as it's thesis and then proceeds to show why and how our concept of operating system covers it -- a book that challenges our comfort in distinguishing operating systems.
Another book I want is "Build an Operating System for $3.47 worth of Breadboarded Chips." There's a book which pushes the lower bounds of computing. Something that provides fertile ground for new ideas.
Write a book at the edges, in the space between computer science curricula and actual practice. Write it just for people who are interested in operating systems. Write it for skimmers and strugglers and dilettantes and professionals. Write it so that people will learn, but also so that some will disagree on conceptual [rather than technical] grounds.
Then it might find a niche.
Good luck.
[1] http://pages.cs.wisc.edu/~remzi/OSTEP/
[2] http://www.linuxfromscratch.org/