44 ms·
> But if you could learn some things from the history and use that to your advantage, why wouldn't you? Everyone would be doing so. Hah! Reasons for not learni
by oblio 10y ago
> But if you could learn some things from the history and use that to your advantage, why wouldn't you? Everyone would be doing so.
Hah! Reasons for not learning from history:
* history is hidden behind NDAs, bad licences and patents
* history is hard to access due to its environment (printed on out-of-print books, stored on tapes, HDD and other forms of storage in someone's basement)
* history is written in a programming language nobody knows anymore
* history is written in an incompatible programming language, one for which there are no stable bindings to your favorite language (or for which there aren't any bindings, period)... just think how many times the String class or data type has been written and rewritten just in something like C, let alone the copies in Java, PHP, Ruby, Javascript, Go, Rust, etc., etc.
There's a ton of (somewhat) valid reasons history is forgotten and most of them aren't "history was bad, let's just forget it".
- pjmlp 10y agoTrue, but many of those hurdles are easy to overcome when one is curious about history of computing, specially since many libraries have been scanning old books and papers. For example, I have collected the majority of Xerox and DEC research papers that I could get hold of.