Hacker News Reader

I'm aware of polymorphism and the list convention and I'm not going to argue against them.

However, the example code uses `c' for connection and `q' for query. Surely, knowing what those are from the variable name would be a good thing?

It's not that I want to impose Obj-C's verbosity but the other extreme (1-letter names) is just as bad.

View on HN

It's not often discussed in polite company, but Haskell programmers are actually not Homo sapiens sapiens. They're a whole other sentient species walking invisibly among us. Their Achilles heel is the keystroke: each one like smoking a cigarette is to us (in terms of damage, not addiction). So while you and I have the luxury of calling something "connection", a Haskell programmer considers that 9 steps closer to fingertip cancer.

> However, the example code uses `c' for connection and `q' for query. Surely, knowing what those are from the variable name would be a good thing?

In this case, the example is short enough that there's no chance of confusion (for the intended audience): clearly c is a connection and q is a request. They're only used in those few lines.

However, I wouldn't say 1-letter names are the norm in typical Haskell code (outside type variables).

Reply on news.ycombinator.com