Hello from a libc-free world! (Part 1)

http://blog.ksplice.com/2010/03/libc-free-world/

JQuery plotting

http://www.jqplot.com/

Identity confirmation

http://www.edentiti.com.au/

Game development in Python

http://pyglet.org/documentation.html

http://matthewmarshall.org/projects/rabbyt/

Clojure & QT

http://lifeofaprogrammergeek.blogspot.com/2009/05/model-view-controller-gui-in-clojure.html
http://dist.trolltech.com/developer/download/webstart/
http://en.wikibooks.org/wiki/Clojure_Programming
http://technotales.wordpress.com/2007/10/03/like-slime-for-vim/
http://tealeg.blogspot.com/2008/11/on-clojure-part-3-designer-uis-and.html
http://briancarper.net/blog/clojure-qt4-memory-leaks
http://briancarper.net/blog/clojure-qt4-system-tray-mail-checker
http://doc.trolltech.com/qtjambi-4.4/html/com/trolltech/qt/qtjambi-index.html
http://briancarper.net/blog/qt4-in-lisp
http://kevinoncode.blogspot.com/2009/01/creating-clojure-gui-application-with.html

Home Physics

http://homephysics.blogspot.com/

http://www.wired.com/geekdad/2010/02/leftover-valentines-chocolate-use-it-to-measure-the-speed-of-light/

Linux glibc Heap Consistency Checking

Heap Consistency Checking

Another possibility to check for and guard against bugs in the use of malloc, realloc and free is to set the environment variable MALLOC_CHECK_. When MALLOC_CHECK_ is set, a special (less efficient) implementation is used which is designed to be tolerant against simple errors, such as double calls of free with the same argument, or overruns of a single byte (off-by-one bugs). Not all such errors can be protected against, however, and memory leaks can result. If MALLOC_CHECK_ is set to 0, any detected heap corruption is silently ignored; if set to 1, a diagnostic is printed on stderr; if set to 2, abort is called immediately. This can be useful because otherwise a crash may happen much later, and the true cause for the problem is then very hard to track down.