"A little more than three years ago there was a thread in comp.lang.lisp about what people were working on in Common Lisp. [...] Let's update this. What are you using Common Lisp for in 2008? What are you using to do it? I'll start [...] I primarily use SBCL on Linux, x86 and x86-64, with Emacs and SLIME. For deploying all my website stuff I use Edi-ware extensively: Hunchentoot, HTML-TEMPLATE, and CL-WHO. I use CLSQL for a few things too. For graphics work, I use mostly my own libraries.

How about you? Leave a comment and let me know."

The latest version of web browser Firefox will make changes to the way people search for information online, says its developer.

It has become a commonplace perception that the UK is rather unenlightened when it comes to open-source software.

VMware today inked a quartet of software deals with server giants Dell, Hewlett-Packard, IBM and Fujitsu Siemens. The agreements will infuriate Microsoft which is struggling to get its own virtualisation offering onto the market.

Adobe has announced that it is sponsoring the SQLite public domain database engine project by joining Mozilla and Symbian on the SQLite consortium. The news is interesting in that it balances Google’s recent sponsorship of efforts to support Photoshop on Linux, while it also raises an interesting question about Microsoft’s attempt to define commercial open source.

A Skype user received a message about security problem with his Windows machine. The funny part, is he was running Linux!

What does Software as a Service (SaaS) have to do with Open Source? Not much, you might think. Or maybe you've noticed that the FSF extended the spanking new GPL3 to the Affero Licence--to deal with SaaS providers? It does not help Open Source Software makers to make more money, so who cares? Well, OSS makers should care, as SaaS may finally give them a business model that may finally bring them some money.

Microsoft irrevocably promises not to assert any Microsoft Necessary Claims against you as an open source software developer ("You") for making, using, importing, or distributing any implementation of a Covered Specification ("Covered Implementation"), subject to the following.