101 karma · joined March 15, 2012
It's a far cry from things like Solid's vision of a fully decentralized web of linked data, but at least it's something.
[2] https://developers.google.com/knowledge-graph/
[3] https://developers.google.com/gmail/markup/getting-started
It's somewhat imperfect as not all forks or mirrors are marked as such by github (if, say, it's a fork of a repository not originally hosted on github), but it works in the vast majority of cases.
Edit: actually now that I look back at it I'm almost positive this is the deeper lack "coffee table".
[0] http://i.imgur.com/qJKSvMC.png [1] http://i.imgur.com/zYDZrtr.png
You can use git add --intent-to-add on your new file (or -N for short), and then use git add -p as usual. You can then use the edit mode to remove hunks you don't want to commit just yet.
Not quite as convenient as on an already tracked file, but it's reasonably usable.
Full disclaimer: I'm am a contributor to the LTTng project.
I'm genuinely curious, I haven't had to deal with Windows systems for so long, I'm not well acquainted with AVG and their competitors.
There's obviously a place for both visualisations and art, though, and the line between the two is not always clearly defined.
LTTng, on the other hand, is a tracer, which means it collects events from the kernel (using the built-in tracepoint facilities) as they happen. It's also possible to trace userspace apps (with lttng-ust), or define your own tracepoints. This has the benefit of being much more detailed, and also has a much smaller overhead.
You might be interested in reading the "What is Tracing?" section of the lttng docs [0], which does a far better job at explaining this than I do.