Dick-waving contest GO!

Heya! Time to check up on the credentials of /prog/. Also, feel free to brag your heart out!

The idea is that you post the languages you have done non-trivial (add trivial if you wish) projects in. An estimate on the number of lines of code might be useful too. I'll start:

Non-trivial:
PHP - Built my own lite CMS (approx. 400 lines)
Python - Currently making a file tagging/rating app (500 lines)
C - Plugin for Etheral (1000+ lines, mostly Ethereal parameters)

Trivial:
Erlang - Built a Linda Tuplespace (school, maybe 50 lines)
Java - Varios crap, the most advanced being a simple board game (school, 200 lines)
Haskell - Various crap, made an adventure game (school, 300 lines)

That's about it for me. Now lets see what Gods of programming we've got in here!

>>29
Props for the Perl job, and no, managers don't fap to Ruby, wish they did. Unfortunately, they are still fapping to Java scalable enterprise solutions.

And you want to replace your C# stuff for Java? Crazy. Pray they want Python, Ruby, Perl, Lisp, anything good that is.

>>30
100 lines operating system, go! I agree that less lines _implementing the same functionality_ are better for many reasons (cheaper, easier, better to maintain and usually better to extend), and I'm always the lazy guy who thinks hard to work less, which my boss values as anything I'm asked to reimplement for some reason ends up being 1/4 of the original and somehow be more flexible (due to proper generalization), but sometimes shit just takes a lot of lines.

And that's as long as your lines are readable, i.e. i++;j++; is not better than i++; and j++;. Code beauty is important, you read mroe code than write.

>>32
Use Python, you don't even need getter/setter shit, just have properties, which may be simple properties, or get/set/delete functions defined in the class. This way you can do stuff like o.p += 2 without all the o.putShit(getShit() + 2) ugly stuff.

line count is a general indication of either complexity or developer stupidity.
Truth