Ah yes, when the only two languages that mattered were C and perl :-).<p>I find it helpful to maintain perspective with "CS" then and now. Many older engineering professions have a 'base class' (to abuse the phrase) and then many sub-classes. For example, there are the basics for Electrical Engineering, but then there are generally specialization areas where people can spend their entire careers (RF, Power, Digital Logic, Electromagnetics, etc).<p>And back at the turn of the century there was pretty much only one "CS" discipline, it was heavy on math, data structures, and language and systems design. The more informal sub-areas were probably OS programming (often called Systems programming), language design, and "Data processing" (which subsumes data base design and use). We have since added many more, networks, web applications, and embedded systems to name a few.<p>We also have "trade" programmers (some folks call them 'CRUD'[1] programmers but that seems a bit derogatory to me) that is more closely associated to Electricians than say Electrical Engineers. They play a vital role in businesses everywhere but realistically don't need all the Math and such that typical CS programs require to do a good job.<p>[1] CRUD - Create Read Update Delete type applications (<a href="https://en.wikipedia.org/wiki/Create,_read,_update_and_delete" rel="nofollow">https://en.wikipedia.org/wiki/Create,_read,_update_and_delet...</a>)
Dead Link Checker:<p>whole site:
<a href="http://cslibrary.stanford.edu/" rel="nofollow">http://cslibrary.stanford.edu/</a>
100% scanned - 116/116 URLs checked, 98 OK, 18 failed<p>root page:
<a href="http://cslibrary.stanford.edu/" rel="nofollow">http://cslibrary.stanford.edu/</a>
100% scanned - 28/28 URLs checked, 24 OK, 4 failed<p>18 dead links on single-page site with 4 dead on the homepage. I'm curious what's the threshold of dead links for considering a site "abandoned."
Why is this being posted? I suppose it's interesting from a historical perspective, for what is available. This is so far removed from modern CS Ed that it's an interesting little time capsule, I guess.
There oughta be a visual/conceptual explanation textbook for Rust borrowing, traits and types because some of it is confusing and/or ambiguous.