If you use Perl in CGI only then you seem to misunderstand lots of stuff. The Perl interpreter is loaded once per FastCGI task, so noone waits.... its the startup (which is then 100times faster against C# or Java, but whatever, not the topic). So please, dont compare Apples with Pears.
Impressive post... Perl Marketing and DuckDuckGo wanna thank you for those wise words :-) (from a guy working for both). Would be nice if you would get into contact with me: getty@duckduckgo.com or getty@cpan.org ;)
You dont need to convince them to switch! You can still talk to your gtalk friends, its all XMPP/Jabber! This is not a service just for inside duckduckgo. Inform yourself a bit more about XMPPP/Jabber :-).
Note the #. Now, remove it and everything after it and reload the page.
Why am I being downvoted? Didn't we all just throw shit at gawker for doing the same thing?
EDIT: This fundamentally breaks the web. The # and everything after it are _not_ sent to the server. It relies on javascript and extra-protocol information to get the document, which breaks the idea of a resource having its own name. The # was suppose to denote a section of a resource, not a resource in-and-of itself. I'm sure everyone here knows this, but I had to get it off my chest.
We at DuckDuckGo assure the same anti-tracking policy on our XMPP server. There is nothing greater about DDG then other sites following the same policy :-). But its DDG :-)
That's cool. But I've no idea if you're retaining IP logs and chat logs. You really need a service specific privacy policy which details exactly what you store and for how long.
A friend did this: https://gitorious.org/irctk ("irctk is a general-purpose IRC wrapper written in C with libircclient"). I think it could be pretty straightforward to do the job using it.
We prefer Perl, cause we got one solution for everything and can easily combine the thousands components offered. Just cause a lib does IRC doesnt help us much :-) It must be easy! :)
