Reading about the Apollo Guidance Computer. Compare that to the US$3.23 ATtiny85.
| Spec | AGC | ATtiny85 |
|---|---|---|
| Word size | 16-bit | 8-bit |
| Clock | 2 MHz | 20 MHz |
| ROM | 72 KiB | 8 KiB |
| RAM | 4,096 B | 512 B |
The values in the above table are approximate, see the sources listed above for actual figures. Basically the $3 chip is ten times faster than the AGC but with less storage. Call it a draw?
lol. My new books arrived:
These are hilarious and fun. The content is available free online on archive.org. The supplementary files are in the same place. (Some of the PDF files are ZIP files!)
Oh wow, just found this from NASA: Earth’s Moon.
$ watch 'grep MHz /proc/cpuinfo | awk "{ print \$4 }" | sort -n'
If you want to get a simple report on your linux system’s specifications, try these:
A good summary of the browser console facilities: Use console.log() like a pro.
Today I reviewed: 5 Best Vector Graphics Editors for Linux. Will play with Inkscape first I guess…
Pat Helland has been talking about data inside the service versus data outside the service since at least 2005. I realised back then when I read his paper that the way to model “data inside the service” in C# was to use value types (structs) which could enforce the format and range of its data in the constructor. In this way you could have a value type, say EmailAddress, which had a single string, an email address, and if you passed an EmailAddress to a function, you know you don’t need to revalidate the data, it’s known safe and “inside the service”. Data outside the service is simply a string until it’s brought inside during the construction of a value type for any given domain. The really neat thing about this is how cheap the value types are, they don’t add any overhead, the EmailAddress example above still has only a single string value, and nothing new or additional needs to be allocated on the heap.