OS X doesn't support Valgrind or GProf. That's enough for me to keep a Linux VM around. Additionally, I've found that software is often easier to build under Linux.
It could definitely be a false positive. That said, that would be pretty strange behavior for a function called getColor(). I'd expect that to return a property value, not modify some state.
I can confirm that MonoDevelop works reasonably well for F#, but the documentation for F# on Mono isn't great. Coming from OCaml, I love F# as a language, but the tooling isn't as good as it is for OCaml. Might be better on Windows with VS, but I haven't looked closely at that.
That's pretty much what Nuitka is. Unfortunately, PyPy is only fast because it can take advantage of runtime information in the JIT. AOT compilation loses that advantage.
I think it still is. The output is a function fitting the data, so as long as that function is amenable to analysis, it doesn't really matter how it's found.
In fact, the paper discusses some modifications they made (reducing the number of parameters) to make the output kernels more intelligible to humans.
AFAIK, the original reason for the DRM was to prevent other companies from selling K-cups, so it would need a way to validate each cup, not just prevent reuse.
It's interesting that his concept for inline search looks almost exactly like a current google results page. It would be very cool to have something like that available without necessarily relying on google for it.
Unfortunately, I'm not sure that a composite view like that, which queries multiple services, can be created quickly without aggregating the data before the search is performed. That's problematic if you want to avoid relying on a single search provider.
It already includes a donation link under the station name. Right now it just sends you an email with donation info. Hopefully they can streamline that in the future.