509 karma · joined July 14, 2010
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.
It might only take two minutes to do, but it's also just botched a nice hour long flow with the context switch.
HTML+CSS offers little to no control of how a page would look like once its printed. LaTeX on the other hand, can be optimized with printable fonts, appropriate margins and such like. A PDF with embedded fonts would guarantee that the page would look the same, printed with any computer/OS/printer combination.
Additionally, if I'm able to get that burst of endorphins from people just by telling them what I've started, then I no longer have a strong enough reason to build up a list of things I've finished.
For OS X 10.7.2, you can grab the source at http://opensource.apple.com/source/xnu/xnu-1699.24.8/.
The "README" at http://opensource.apple.com/source/xnu/xnu-1699.24.8/README has instructions on building and installing the kernel. Admittedly, while I have never actually done this, I've seen lots of instructions floating around for doing this "correctly".
Thanks for the link anyhow! I'm pretty sure I'll be able to use them for a different project.
No idea why the appcelerator page is the main story link.
I'd venture to guess that the $300 million aren't for beating Apple, but for nurturing and mentoring the company that will replace Apple as Intel's primary/flagship notebook processors customer.
That your software is open-source is entirely orthogonal to the issue of infringement.