← Back to context

Comment by Verdex

1 year ago

In the past, I have been unimpressed by this paper. Perhaps someone can shed some historical context...

But from my perspective what happens is that the paper defines complexity in exactly the way that allows them to deride OO, FP, etc programming whilst simultaneously showing how awesome functional relational programming is. It ignores complexity that's orthogonal to what FRP addresses and ignores areas in which FRP itself contributes to unnecessary complexity.

It feels like a scenario where the authors had something that they thought was neat and went out to create metrics that would in fact show that it was neat. Maybe FRP is really neat, but I feel that the paper itself doesn't contribute to anything because its logic is so custom and purpose built.

I think the first half of the paper ("the problem") is much stronger than the latter half ("the solution").