gnok
Joined 16 years ago
Joined 16 years ago
The gist of it seems to be that its a set of data models that make handling concurrency control and conflict resolution easier in the context of a single blob of data being edited by multiple users simultaneously (similar to Google/Apache Wave)
I don't know either way, but I sure wouldn't assume its designed for the exclusive purpose of "helping hipsters heap hi-res headshots of healthy hobos" (nice alliteration btw).
I think Yahoo's problem with acquisitions has been that they are moderately successful initially and then drift away over time. ViaWeb, GeoCities, Musicmatch Jukebox, Konfabulator, delicious and Ludicorp (of Flickr fame) come to mind. Other than Flickr, none of the others are still around, but they weren't disappointments soon after acquisition either.
Google is no genius with large acquisitions either. Motorola and Blogger come to mind immediately, but there are others too.
I think we can all agree that Yahoo has been mismanaged at least until recently. I just don't think a CEO's performance is a boolean value that depends on an undefined "any sign of failure" on a large acquisition with a 1 year time frame.
Makefiles solve a different problem; which is of local build dependencies, looking for changes, packaging and suchlike.
CMake, as it happens, was written because Autotools were particularly ineffecient at the configuration problem. Make happens to be very efficient.