That's Whitney's style. My preferred example is http://www.kparc.com/b/b.c

It looks obfuscated, but in fact it is just a lot of information. Many people would claim dividing it in 10 files with longer function names and less tricks would make it easier to understand, but after spending a long time studying (and partly rewriting) this code, I actually find the terse version better.

The problem with satire is that no matter how far over the line you think you've gone, someone will always wonder whether you really meant that.

> after spending a long time studying (and partly rewriting) this code, I actually find the terse version better.

I'm sure Mr. Goldberg understood his machines just fine, too.

I've tried Whitney's style and got some good takeaways from it. I don't need that level of density, but it made me realize that when the code is already doing something very abstracted from business logic, there is no sense in trying to name the variables with more than one or two letters. (x0 and x1, appearing in geometric functions, are favorites of mine.)

I also started using "result" after seeing it in Pascal code and have quite liked it for many years, but I just had the epiphany that "ans" (answer, as seen on several graphing calculator lines) would be a little more dense.

Basically, it was well worth it to try these radical styles out. They did a lot to smooth my everyday coding.

Or anything APL-related, really:

https://news.ycombinator.com/item?id=13565743

https://news.ycombinator.com/item?id=13797797

:O that is ... interesting. Sure that's not an entry for the ioccc? ;)

Nope :) This is being used everyday in production by most financial institutions. https://code.kx.com/wiki/Cookbook/InterfacingWithC

I've been told that the guy who wrote this believe that the brain only has a limited buffer to compute source code. So he is trying to use the shortest code possible everywhere.

I think looking at this code has already caused a buffer overrun in my brain ;)

"This is being used everyday in production by most financial institutions" — you can't be serious...

KDB developers make BIG money. It's an APL-like language and used to analyze financial time-series.

I'm not surprised, it's an APL family language.

It looks more like the guy that wrote this wanted good job security and pay, and ended up making and industry with good job security and pay.

that's just for writing c interfaces to kdb.

As someone who writes q all day, it's typical to see functions written in one line and no white spaces. The mantra is, if it takes you more than 1 line you're probably doing it wrong.