A Modern Programming Operating System
31–34 of 34 posts
Re: A Modern Programming Operating System
#32Any recommendation other than plan 9 is seriously considered harmful.
Re: A Modern Programming Operating System
#33Earlier quoted context omitted.
What's wrong with learning kids Shell scripting? Assuming you mean bash-like shells on Unix boxes, quite a few things: 1. Commands have arbitrary, hard-to-remember names. 2. Destructive commands tend not to issue warnings. 3. Mass destructive commands still tend not to issue warnings. 4. Did I mention that destructive commands don't tend to issue warnings? 5. Destructive commands typically can't be undone. A system w…
I meant that you should setup a simple environment, setting up a partition and chroot into it. Learn the kid to use man(1) and ed(1) and after that let him/her play around. I heard someone doing this with his 5 year old kid on the OpenBSD mailing-list, that kid will probably be able to write quite useful scripts in a few years.
Re: A Modern Programming Operating System
#34What's wrong with learning kids Shell scripting? I think most Unix-like OS's are good for learning, behind the complex layers of abstractions lay the simple command line. Excellent for programming without any distraction.
What's wrong with learning kids Shell scripting? Assuming you mean bash-like shells on Unix boxes, quite a few things: 1. Commands have arbitrary, hard-to-remember names. 2. Destructive commands tend not to issue warnings. 3. Mass destructive commands still tend not to issue warnings. 4. Did I mention that destructive commands don't tend to issue warnings? 5. Destructive commands typically can't be undone. A system w…