"Why", not "how". I read this in 3rd grade, probably around 1967 or '68? Piqued my interest in computers that lasted and that I finally got to explore senior year in high school. One thing I
/think/ recall from the plot is suspicion that Danny was cheating by using the computer, but it turns out he needed to undestand the problems & the solutions better than the other kids in class in order to be able to do the programming. http://www.scholastic.com/browse/book.jsp?id=854
That was the name of the textbook, and we did it on an HP 3000 timeshare minicomputer in 1976. First high school in the city to get its own educational computer system, I think. The class was "Computer Math", and it changed my direction from architecture to computer science. Spent 4.5 years at the state's science & technology campus helping my engineering major friends with their mandatory FORTRAN class.
:-P In Computer Science in those days we did a lot with PL/1. Got a job in a small shop after graduation and was in the right spot at the right time just when Unix got commercialized and I got the task of figuring it out. :-D
I've had multiple videos flagged by YouTube as using music belonging to some commercial entity when in fact they use variously licensed tracks from freesound.org and ccmixter.org. Dunno what to do...
I use elinks when I know there's going to be pictures of scary ugly bugs on the page. Like when researching when those periodic cicadas will be coming out. Ick!
Why does the government need to guarantee loans? Because it doesn't make enough sense for sane people to back. If it will pay for itself and give reasonable return while generating cost-competetive power, it doesn't need the governement guaranteeing it with your money. Unless they've already succeeded in their campaign to destroy the ability to raise free capital in this country.
Nah, I didn't really learn anything from that article, but I'm not too surprised. But there's still value in it by being a seed to
/. to get all the contributed ideas and alternatives you see here.
Most times I read
./ just for the story links and disregard all the idiot responses. But on a story like this I figured I could get some useful pointers from the discussion, and I did.
Most times I read
Ten years ago many readers here were probably raiding Dad's cache of floppies, not buying their own. Not most, perhaps, but many.
I find man pages to usually be concise, to the point, and extremely helpful. I hate it when I find there is no man page for a program for which I have a question. I remember when we got our first Unix Sytem 3 v7 system in the '80s. The entire sum of the documentation consisted of one binder of man pages, and one binder of troff-formatted documentation on things like flex, yacc, troff, etc. And it was sufficient for an intelligent neophyte (yours truly), but it certainly wouldn't be suitable for Grandma or my accountant.
The problem with mitigation techniques that rely upon some ongoing activity is that when it is disrupted for any reason, the accumulated upward pressure on temperature is still there which could have sudden, catastrophic effects. (Regardless of whether I'm conviced of the anthropogenic causes of climate change.)