That is an interesting argument --- maybe there could be a tax credit for publishing specifications/keys when a product is end-of-lifed and support is cut off? Or, maybe a company could be required to pay for disposal if that is not done?
I'm actually rather fond of OpenSCAD --- it has the advantage of being completely safe in terms of security/execution, so no worries about downloading a random .scad file and wondering what it might do.
If one wants a full-fledge programming language for this, I found Python a lot more comfortable:
For my part, I've been working the CNC router angle, so have a much larger kerf to cope with (and the added advantage of controllable partial depth and no char):
Recently I've been on a kick making bracelets with that frame loom. The rotating heddle bar makes it super quick to warp up. I've written about how to go from woven rectangle to bracelet here:
The best programming course I had in college was one on comparative programming languages (and not just 'cause I was the only student who was able to do all of the Lisp exercises solo) --- it was quite striking getting an overview of the history of computer science and to see the myriad approaches which had been used.
Until the stack got too large, or one forgot the ID of the card one wanted to link to or the search text which would allow one to make it a target, &c.
HyperCard was _amazing_ (and I still have my copy of _The Manhole: Where Alice would have gone if Alice had HyperCard_ which was the predecessor for _Myst_) and it kills me that we lost MacBasic:
and that HyperCard was such a mess of licensing that one had to use the "magic" word, or a command to enable Developer Mode and that it took so long to be developed/released:
(though one wonders what would have happen if it had instead been a NeXT product)
and then of course that the various alternatives had such tortured histories and of course the infamous "rug pull" when Live Code went closed source --- is there a viable free/opensource implementation which is nicer and more usable than Decker?
There was a commercial networking product which addressed principle 13 as well --- Kerbango? I remember a couple of ads for it, the idea was that adding a computer to a network and installing this would increase available storage space and back up all the other computers running the software on that network, basically a RAID of compleat machines....
The other books on hardware from this timeframe such as Tracy Kidder's _The Soul of a New Machine_ or Jerry Kaplan's _StartUp_ or Andy Hertzfeld's _Revolution in The Valley: The Insanely Great Story of How the Mac Was Made_ (available as: https://folklore.org/0-index.html) are quite striking and forthright in their discussion of hardware limitations and the ingenuity needed to get things done.
Or, contrast the far more prosaic _Weaving the Web_ by Tim Berners-Lee and esp. take note of compromises such as URL changing from Universal Resource Locator to Uniform Resource Locator.
Visit any older cemetery and look for the tiny headstones and the matching very brief lifespans, or read an older obituary for someone from your great-grandparent's generation or further back, or watch a couple of seasons of _Call the Midwife_.
reply