Thing is, these are really hard problem to solve, since they are essentially all about moral values, which are always subjective in nature.
The technical bit is just about the least significant; you could probably make a really accurate dog vs. human detector, but -like all software- it won't ever be 100% free of bugs.
This is why lawyers keep bringing up the problem of who is responsible in a self-driving car.

If you can legally get content for free, you'd be stupid to pay.
If you can't, you'd be a asshole to take it for free anyway.

It also means that the cars aren't driving autonomously at all times.
To me this implies that there simply isn't any comparable data yet.

How about choosing whether to run over a toddler or a baby?
You really can't blame cars for not being able to make value judgements like that as no sane human could.

You may not be able to buy them yet, but they're certainly already selling you on the concept of it.
The fact that we're talking about it here demonstrates that the marketing department for these cars is already in full swing.

This. I do both open source and some small commercial software on the side. I always make sure my contract includes terms that allow me to continue doing that as long as it doesn't compete with my employer. Despite some of the feelings here, employers are generally nice people like other humans.

"Fair" is just a matter of asking the employer. If they say yes, then selling the code is okay, if they say no, it isn't. It's that simple.
If you don't want to ask, consider a "no" by default, because that's probably what your contract says.

Because not all websites are personal blogs. The modern web is a dynamic and interactive thing.
Imagine how badly even something as trivial as a webbased game could be backed up as a static backup.

Not quite the point you're trying to make here, but why not just print out the website and patent it?
Doesn't need to be an invention or novel or anything; modern patent offices will rubberstamp anything, and it'll be available for atleast several decades after you die or until Disney goes bankrupt and can't bribe politicians for extensions any more.

The return of WAP sites.
Are any of them still around?

Why do sororities even exist?
They seem like an utterly retarded idea.

https://github.com/search?utf8...
Javascript wins.

PHP developers prefer murdering kittens: https://github.com/search?utf8...

Some other fun facts:
C developers are most ashamed of their code: https://github.com/search?utf8...
PHP coder don't fix bugs: https://github.com/search?utf8...
C developers' code actually get worse as it ages: https://github.com/search?utf8...

Java developers seem to have the most trouble getting their code to work: https://github.com/search?utf8...
Not surprising: https://github.com/search?utf8...

Disclaimer; not corrected for any type of bias or error, of which there are many.

Or maybe they're simply aware of what is ugly and what is not.

I develop PHP for a living and a while back I encountered a styleguide which said you should give function arguments. Code like 'function f($a, $a, $a) actually works in PHP. This in itself this as insane enough, but... some developers are retarded enough to require a styleguide to tell them not to do that. You think any of those developers will be able to tell the difference between an ugly hack and good, clean code?

My guess is that most of this is just down to C developers generally having a better understanding of what is and is not ugly code.

Achieving 99.99% bug-free is infinitely more expensive than just 99.98%.

No offense to the awesomeness that is Hubble, but isn't it logical for it to break distance records on a regular basis as more "old" light reaches it simply as a function of time?