924 karma · joined July 9, 2011
Their policy is to take down any content that is available commercially. IE: once the box set comes out, you can no longer share it. Other specific content cannot be shared even if there is no non-commercial source. It is easy to get banned from the service, so users are very compliant.
There are a lot of expatriate Brits who will miss the service, not to mention fans of British TV everywhere.
Disclosers gonna disclose. Know what I'm saying?
The response from the AOL spokesperson makes it seem like they are taking the incident in good humour:
"It was always our intention to facilitate entrepreneurialism in the Palo Alto office -- we just didn't expect it to work so well."
It is direct, concise, consistent and tends to active voice rather than passive voice. Further, not everyone writing or reading the messages will be a native English speaker. Avoiding past-tense forms just makes it easier.
It was noteworthy for the coding discussions.
"Q: How do you rid the world of illegal drugs?
"A: Legalize them and put IBM in charge of marketing."
I can relate as a one-time business partner. Our biggest competitor was IBM Global Services. Once we even had a teleconference to discuss going after an opportunity. We dialed in, but no IBM. After waiting for 15 minutes, we called someone who was to be on the call. "Oh... we decided to do it ourselves." Didn't even bother to tell us.
CA (Computer Associates) made this their primary product revenue stream by buying up old software (eg. Clipper, Ingres, etc.) that still had an installed base. They invested minimal amounts into product maintenance (make sure it works on the newest version of Windows) and rake in the licensing revenue from the remaining user base.
The only thing different is that Adobe is essentially doing it to themselves--monetizing their own long tail instead of selling to a long-tail specialist and moving on.
The question then, is it in the public interest not to cover this story. I'd say it would probably not matter so much from a security standpoint, but more so for the amount of mayhem that could ensue at airport security if this was public knowledge.
At your best you can become antibodies in the global cultural organism.
I do have a theory that a lot of the people who engage you in smalltalk also have similar dislike for the practice, but they've been assured again and again that this is something they must do.
I didn't get out of bed when I woke up, but I found I was extremely lucid. As soon as I could use the time for problem solving, I stopped waking up :(
Definitely look for opportunities to collaborate with others--working with a like-minded team can push you further than you could get on your own. Contributing to open-source projects will be a boost too.
The things about git that make me like it better are that the branching and merging are easy and the distributed nature of the system. If your development process doesn't exploit the features of git, then svn would be a reasonable choice.
EDIT: Another key thing I like about git is that repos can be nested. The parent repo simply ignores the child repos. This is something where I get a lot of benefit.
Also, the risk of S3 pricing changing greatly is constrained by the wide adoption. If DynamoDB failed to become pervasive, it would be relatively easy for Amazon to increase the price to make an underutilized service profitable. OTOH, if DynamoDB does become as popular as S3 your exposure to risk will be much less.
I'm certainly not going to commit to platform lock-in like that. I know a lot of folks were hit hard by Googles app engine price changes and it could happen again here with DynamoDB.
There's a few command line parameters to learn, but after that it is so simple, efficient and reliable that there is no need for a GUI client such as the various FTP FTP clients. I typically write scripts for specific purposes, syncing only the files that have changed. Using my SSH key means I don't have to type the password all the time.