The old UK sci-fi television series, Blakes 7, which aired in 1970's had this as one of their predicted technologies.
Entire portions of machinery would regenerate after being exploded in sabotage.
Grids of "radiation mine wire" would after being cut, would have the ends of the cable seek each other out and it would grow to join up again. The strategy to bypass this grid/minefield of interlaced wire, would be to fire the blaster across it clearing a path and then to run through it within 8 seconds before it regenerates.
While it was a bit fantastical for the time, I'm sure some hand-waving could justify nanotech as the way this TV tech might be realised.
Worse than that, I used to be very knowledgeable about a topic and having not played the game and not scored any points, it was too frustrating to answer questions there.
The unfortunate thing is that people often see it as the github of project support, and choose to go there to ask questions rather than a project's mailing list.
I have home edition, it is set to reboot in the middle of the night. The laptop goes to sleep or hibernates when I go to bed, one or the other, the update is still pending when I start the laptop in the morning. Updates can be put off indefinitely, if this is the normal pattern.
Have you tried to read a page on facebook without an account? It's intended to be an almost unusable experience.
On loading a page, I get a modal popup obscuring all content insisting I "register" or "login", with a "not now" option. Then when you click "not now", the bottom third of the screen is obscured by a fixed overlay.
It is loosely describable as readable, but in practice, it's a fight to read it. The element has randomly generated id, so can't easily be blocked with ublock or similar.
Make that 7km, at 7km/hr, 3 times a week and I believe you hit the sweet spot of the Danish study that came out a couple of years ago.
If I recall correctly, it monitored ~20000 people over ~19 years, and provided bell curves of the best benefit.
I used to jog every day for an hour, and it was bliss. I miss it. Any day I don't get up and go for a run, I feel like I am worse off for it. But I'm trying to migrate to the above.
When I programmed in university pre-2000, I used gopher in place of google.
Applicable matches were limited to source code file search, which gave examples of function calling out in the wild. There were no books of use available, and the documentation was often vague and incomplete man pages.
It mentioned unlimited guests to meals, with an open bar. As well as something like a gym washing service. It's clear in the article that there were more than meals, with these given as specific examples of cuts.
Back before decent search engines, there was gopher or ftp search. I used to search for function names or some part of some API in gopher (or ftp search), and find source code in projects where the code was already in use. Then use that to get hints about where I was going wrong.
Google and StackOverflow fill a much wider niche however.
> Everything we do at Facebook is focused on our mission to make the world more open and connected.
I often find that when I follow Facebook links, I get a login page, requiring me to create an account to see the content.
And not even for Facebook itself, I tried to look at images on Pinterest the other day, and if I followed more than one link, I'd get an overlay requiring me to login via Facebook. The site was almost unusable if I wasn't logged into Facebook.
The only other sites I've visited in a long time, that hide content unless I login, are newspaper sites.
I quit drinking coke zero on purpose for months at a time, and come back to it, just to appreciate it again. At no time have I ever thought it tastes sickly sweet.
There are <a href="http://eab.abime.net/showthread.php?t=80875">comments on</a> one of the Amiga communities most popular forums by a Olaf Barthel, a developer who modernised a more complete version of the 3.x source code. He relates that you need several different C compilers for different parts of the OS, from one that needs to run on a Sun OS to various Amiga-based compilers (Aztec/Manx).
Similarly, back when I used to maintain Stackless Python and do merges in from mainline Python, my benchmark was to only have the same set of failing tests post-merge for the same merged revision.
More often than not I would have failing tests in official Python release version tags, which became par for the course.
All my different devices have shoddy software. From every smart phone I've bought to smart televisions and not so smart satellite decoders and bluray players. None of them have source code available to fix the problems, and the firmware is more often than not encrypted.
There has to be some solution to the problem of low quality and ill-maintained vendor software - but to them it's not a problem so much as a push for the user to do a device upgrade.
Now there's just a bar I'm ignoring that's obscuring part of the useful information.