Aren't Aereo antennas storing TV signal content on servers and retransmitting/uploading that content to multiple members of the public? That's what's prohibited by copyright law, according to the broadcasters.
No. When you activate the Aereo service, you are assigned a dedicated (not shared) antenna and the video is streamed from that antenna to your device. There is no storing or sharing of anything.
IMHO, this ruling was not surprising. The justices were openly hostile to Aereo and saw it as basically someone setting up a cable company without following the rules set up for cable companies--mostly the part where cable companies pay local stations for the content they rebroadcast. The thousands of tiny antennas did not impress the judges.
I don't think there's a second-system effect going on with Perl 6. Every two or three years some new team has come along and tried to implement it, only to totally fail and produce nothing usable. These people didn't implement Perl 5, so I don't think we can say that Perl 6 is a second attempt for them.
Nope, this is exactly what happens with the Second System effect. Everybody gathered up all of the ideas that percolated and were grafted on to Perl 5 and wrote a huge requirements document for the next version. Then when people try to implement it they discover that it takes way more effort than they expected and fail. Repeat a few more times and you have a language that either never comes out, or finally appears from a single vendor and costs a small fortune because they had to pour so many man hours into it. Even then it's buggy and slow and most people never touch 90% of the features because it's way too big to grok and even the reference manual is a monster. Plus, a lot of the tertiary features are poorly tested and likely buggy.
The proper solution is to build a small(ish) but relatively clean core language and have a robust module system to let people pull in only the features they need, and to let developers focus on relatively small parts of the design and get it right. Perl5 actually does a pretty good job of this, but it could use some fixes here and there.
Requirements documents are a two edged sword. Without them you end up with a hodgepodge language (see: Perl 5), but it's a lot easier to write requirements than it is to fulfill them. Put too many in there and the system becomes colossally expensive to build. This is the primary reason Government work is so inefficient, because simply writing the requirements and then verifying that they were followed is an enormous job, and training everybody in what their specific requirements are is also a massive undertaking.
Kleeneness is next to Godelness.