I'm dubious.
Functional programming is great for some things. But the reason you can mathematically prove it's correct has to do with the lack of side effects in functions. As soon as you put a SQL database in there you lose that property and it's no longer truly provable functional programming.
He talks about two special features, encapsulation and simple concurrency, as if they're some new mind-blowing thing that most web developers have never heard of. Anyone using a modern web development language like ES2015 or Coffeescript, and a library like React, has access to both of those.
So, interesting experiment, but it doesn't seem worth the trouble of dealing with the limited libraries and servers of a niche tool. The toy example in the paper aside, I doubt there's any meaningful productivity boost unless, like the author, you think mainly in functional modes all day long anyway.
He talks about two special features, encapsulation and simple concurrency, as if they're some new mind-blowing thing that most web developers have never heard of. Anyone using a modern web development language like ES2015 or Coffeescript, and a library like React, has access to both of those.
So, interesting experiment, but it doesn't seem worth the trouble of dealing with the limited libraries and servers of a niche tool. The toy example in the paper aside, I doubt there's any meaningful productivity boost unless, like the author, you think mainly in functional modes all day long anyway.
