I was hoping to find out whether I'm actually as lazy as I thought... :(

I clicked for the same reason.

Might be worth changing the HN title to be more descriptive. My suggestion: "What Lazy Evaluation Really Means"

Yes I know it undoes the cutsie title, but he's just going to deliver a bunch of bandwidth, get no ad clicks, and waste a bunch of people's time.

> he's just going to deliver a bunch of bandwidth, get no ad clicks, and waste a bunch of people's time.

Precisely how I would evaluate this comment!

I'm not sure if you're being self-referential or not.

If you need to know that for this particular argument, I guess you'll have to wait for him to return. I can't make promises on his behalf though.

I'll have to leave a callback then.

or maybe "What It Really Means To Be Lazy (evaluation strategy)"

Let's just go with yes for now. :)

I am not so sure the example provided helps me understand its real use. To me his example resembles something the compiler would handle by filtering out code that is never used. I suppose that the example could be more complete with a conditional use of F3 later on, implying if the condition is not met then C={F3 30} would be skipped.

Appreciate the article, confused me at least which means I will probably look into such ideas more even if in my field I will never use them

I really appreciate this thorough book review. I've had CTM for a while but never understood whether it was sufficiently valuable to read. I'm still uncertain, but I understand at a much greater depth what I might learn.

OT: I love the design and layout of this blog.

Yea, I obviously put too much effort in to investigating this issue.

Not bad, not bad.

I think I might leave it until I need to know what laziness is about then :/