Dunearhp

It was installed by default on one of my old debian boxes. The first time I stumbled upon it I felt like I was in the twilight zone. It took some time to realize what it was.

It is one of the few arguments that doesn't first require the other person to have a deep understanding of functional programming.

Try to convince someone of the value of immutability without mentioning concurrency.

Imperative and functional programming relate in the same way that arithmetic and algebra relate. It is hard to do deep reasoning in maths without algebra and it is impossible to evaluate the value of most algebraic expressions without arithmetic.

There is a reason that functional programming is at the forefront of concurrency research. In the long run, imperative only approaches will be unable to compete, and functional only approaches will remain on paper.

You can be a good bricklayer without knowing much about structural engineering. What happens when you want to build something taller than ten stories?

What happens when you want to program for more than ten CPU cores?

This is what I think they are doing.

Why does someone need a reason not to answer a silly question.

Do you use EV to run your Perl web apps as free standing applications? Or do you use it for some other purpose?

Your point is invalid, and is in fact a much better argument for open standards, which don't require a predatory monopoly to benefit the ecosystem.

Consider: The value of TCP is not in itself, but in the applications that run on it. The greater the market share of TCP, the greater the utility of the applications. The greater the market share of TCP, the greater the incentive for applications to be created for it.

----

The value of Posix is not in itself, but in the applications that run on it. The greater the market share of Posix, the greater the utility of the applications. The greater the market share of Posix, the greater the incentive for applications to be created for it.

It is an interesting video.

Quick summary: Node.js is a program/api written in C that lets you write asynchronous servers in javascript. All IO is done through event loops and callbacks.

If you are interested in the efficiency/architecture of server programs then this is worth watching.

He confuses his own internal mental model with the actual nature of electricity.

Mostly this is just arguments about semantics.

They've moved the hosting to Australia.

I've been using HStringTemplate on top of happstack quite happily. REST would be fairly easy to achieve using this approach. I would venture to suggest that most people would find it easier to adapt happstack directly to their needs than trying to use happs at this point in time.