[cliffchang]

I used K in an internship in college (DB stuff for a data company whose clients were mostly financial companies). The learning curve was really steep, but once you can parse it, it's incredibly fast to program in, incredibly fast to execute, and generally awesome.

We had a vague guideline at work that if any algorithm took you more than 3 lines, you were doing it wrong.

Legend has it that Arthur Whitney wrote the compiler in a few files - a.c, b.c, c.c, up to around q.c, with each file being exactly 52 lines and 80 columns so they could all fit on one page.

See "no stinking loops" at http://www.nsl.com/ which has some great examples of really good K code (scroll down a bit).