This website has lately been totally unusable, due to the dark-ux workflow at "https://guce.oath.com/collectConsent/partners/vendors"... I hope they're conscious of the traffic they lose. There's no obvious way to dismiss/slip through and be sure that consent has not been given to third-party data collection. Just saying, not the first time I stumble on that f*ckery. Schade!
Urchin 4 continued our tradition of supporting way, way too many random platforms (Google still has Urchin 4 help: check out the OS support… ever heard of Yellow Dog Linux?).
Heck yeah! Yellow Dog was one of first GNU/Linux distro I attempted to use, back in 2k2 (Or was it SUSE 6.4? Both ran too sluggishly for desktop use on my 5400/120, tho.)
On one hand, it was easy to overlook this issue, and you'd end up with catastrophic data loss (been there, done that).
On the other hand:
1. it's the sort of mistake you tend to learn quickly not to redo ;(
2. a variety of encoding schemes were pretty common, and usually integrated in Mac browsers, mail clients, ftp clients. See for example this page from the Fetch website (http://fetchsoftworks.com/fetch/help/Contents/Concepts/Uploa...), or the hexbin(1) man page.
My personal take on what killed MacOS is this.
The MacOS was, for the start, a clever pile of kludges, for 68K series CPUs. Hot patching of routines was how you fixed bugs, introduced support for new hardware, etc. (See https://en.wikipedia.org/wiki/Macintosh_Toolbox#Advent_and_i...) (Btw, a System 7.1 source code archive leaked years ago.)
I can imagine debugging and extending it became more and more painful. And core data structure choices (16-bit-friendly) might have been becoming wasteful as architectures came and went...
So Apple had people grinding at Copland (apparently didn't quite make it), and then NeXT was bought, .
TL;DR: IMHO, that's not the main point (not either a notable one, once you're educated about it). MacOS grew to a point where it became a fragile, quite complex, house of cards.
You have attempted to access a blocked website. Access to this website has been blocked for operational reasons by the DOD Enterprise-Level Protection System.
If you're on a budget, you could get a lenovo X200 Tablet, fit a new battery and 8GB of RAM. You get a nice touchscreen which you can orient as you please and 2 minipcie expansion slots.
That is, if you don't require modern OpenGL/gpgpu features, nor plan on doing massively parallel jobs on it (It sports a Core(TM)2 Duo CPU L9400 @ 1.86GHz)
Hypothetically, you _could_ solder a faster processor (not realistically for most of us tho).
Why the X200 and not a more recent one? They changed the keyboard / buttons afterwards, for the worst :(
NB: you might want to patch the bios to remove the mpcie whitelist ibm/lenovo put in. Misewell flash coreboot (requires in-circuit programming, due to flash block write protection)
After updating qt5base-dev using debian experimental, and adding -fPIC to the CXXFLAGS, it compiled nicely :)
edit: there seems to be a slight problem with text rendering tho(only lowercase 'a' and bullet points are drawn), see http://imgur.com/MiX1hvL More of a qt5 issue I think
This looks _very_ interesting (from a DIYer point of view), however building under GNU/Linux amd64 isn't seamless. (Missing --std statements in the Makefile, notably)
I find openscad quite painful to use, I whish I learned about Antimony before.
I think this has lot of potential, as a lightweigth, intuitive, free software, notably in the maker/diyer scene.