The first thing I wanted to see as a Smalltalker was how much they've baked Blocks into the libraries. I know Cocoa has always had very long method names, but some of these names are wild:
- #enumerateObjectsUsingBlock: is #do:
- #objectsPassingTest: or #indexesOfObjectsPassingTest: are #select:
The interesting thing from my point of view is that the Delicious Library iPhone app doesn't make Amazon API calls for ISBNs. It synchronized with the desktop version of Delicious Library, which gets its information from the Amazon API. So the headline is pretty carefully written, they're killing mobile apps that use their data.
I refreshed the deactivate page, and it doesn't seem to be completely random, but it also isn't 100% the same every time. It seems to pick between the same 20 or so friends for me.
Another thing that's interesting is that the deactivate option is exactly where it should be, rather than buried many levels deep in menus. I tried to remove my classmates.com account the other day, and it was a mess.
I don't understand why you need obfuscation for this. With customers of this size, you can have them sign a contract that protects your IP. Price in what you think is the risk, and insist on a contract.
This is something to be proud of, and github is great work.
It's not really accurate, though because this lists every user's fork of a gem as a distinct gem. Here's a script I put together to get a different count, which I believe is more of a "real" count.
I'd like to read about these, particularly about how they could be Constitutional, but I can't seem to find the correct words for a Google search. Would you post a link, or possibly a set of words to search for?