.net .net framework 4.0 ado.net android appengine applescript astoria beos bi c c# c++ clojure cloud clr cocoa touch concurrency couchdb cql curl data services database django dlr dynamic ef entity framework erlang exchange server full-text functional gnome go google gpu groovy haiku hpc html indexes io iphone ironpython ironruby java javascript jquery jruby jvm linq lisp lucene mac math mirah mongodb monitoring natural language nlp node.js object oriented objective-c operating systems oracle orm parallel performance podcasts powershell prototype python rails refactoring remoting reporting services ruby scripting security simpledb solr sql 2008 sql server ssrs systems programming testing tools vala vb virtualization vs 2010 web services webdav windows xml

C from erlang via linked-in driver (Wednesday, September 16, 2009) - Erlang truly is a useful language. It's fast, full-featured and elegant. Like all high-level languages, however, you sometimes need to access legacy or system code written in another language like, you guessed it, C. I came accross this situation recently when porting my webcrawler to erlang. Under pressure http:request proved to be unreliable when used in

GPU-Based Computing in C with NVIDIA's CUDA (Sunday, January 09, 2011) - At work we do plenty of video and image manipulation, particularly video encoding. While it's certainly not a specialty of mine I've had plenty of exposure to enterprise-level transcoding for projects like transcode.it, our free public transcoding system; uEncode, a RESTful encoding service; and our own in-house solutions (we're DVD Empire, BTW). Of course my