My favourite languages are those which have stand the proof-of-time. I'm in the "backward-compatablity-preferred" camp, but can see also reasons why others won't follow. However I feel very unpleasant about libraries which change from one minor version to another in a incompatible way.
I've spend the last 10 years or so on languages development and my pets peeves are the so called 'non-mainstream' languages. The languages I like the most are currently
* C (see e.g my homepage)
* Common Lisp (well you guess that, I guess ;-)
I do like also: * Ocaml
* and a few others ;-)
I have a dislike for C++, Perl
I'm undecided about Java, C# and maybe a thousands more (because I simple do not know them ;-)
I've spend quite a few years and a bunch of money on developing a follow up language to Eiffel called Q. It's a proof-of-concept it has not materialized really because it seems there is not market for development tools on Linux.
As you might think: I was once an enthusiastic Eiffel programmer, but political reasons from two of the major players ISE and the 'free' (beer) development team of Smart(ll)Eiffel have driven me far away.
Feel free to visit new:comp.lang.eiffel or the Mailings list to get an idea about this stuff.
InvitationWell I would appreciate if you'd start working with me or with anyone else on webDevelopmentExample.
An Essay about whyGary King asked why?The web application development tutorials Maybe some of you have notices that I havn't wrote a line within a month. I'm a bit sorry about that, but I'm really running short on time and temper. As I wrote here: Why answer
The comment from Daniel Barlow just stresses my point:
There I was thinking that the question was why Lisp hackers don't use it for web dev, but then it turns out from the comments that it's actually why people doing web dev aren't lisp hackers.
Lucky I didn't waste my time answering the wrong question, then ..."
From the Blog of http://www.metabang.com/unclog/publisha/why.html answers.
Comparisons between the diverse Web Development Kits
I spend a few hours to get into kpax and it seems that this framework lies in betweeen webactions and ucw in regards to functionality. IMHO it's complexity is in between also, but I've the impression that kpax is the best written from the the mentioned tools. However it may be that this is due to my growing knowledge. So maybe it looks a bit easier as it really is.
But one thing I found very interesting (or amusing) that's the way I wrote my extension for webactions