Either way, FP is slowly eating the web. "View as function of state" has thoroughly won the argument. What that will ultimately look like is unclear, but ignore it at your own peril.

It’s not just eating the web, * as function of state is generally the trend in many disciplines. So much so that people I knew who balked at the concept have since embraced it. And it is good.

Now we just have to get a handle on all the leaky stuff at the edges of every “functional core”, because there lay many dragons.

I want this to be true. And certainly there has been a lot of progress towards functional-ish code in the languages I'm about to reference.

In my experience, languages like C, Go, Java, C# still dominate the backend. Replacing JavaScript is such a simple and well-defined task that I expect it will be completed much sooner. Maybe only a decade or two.

Well I can’t speak to most of those, but I can definitely speak to JS: pretty much the only things holding back FP are people’s aversion to reduce and their aversion to grafting monads where they don’t fit. Otherwise it’s pretty much idiomatic to write functional-core code in JS basically everywhere. But again there be dragons at the edges.

Java and C# can absolutely be written in an FP style and it is definitely winning grounds.

Like I said. Functional-ish. Still way too many ThingDoers and other associated boilerplate to be actually interesting. A nice option though if you're working in a legacy codebase or your employer requires it.

> Now we just have to get a handle on all the leaky stuff at the edges of every “functional core”, because there lay many dragons

My gut is telling me erlang might have tackled this.

Don't worry. It didn't.

surely "reducer" came from early FP leaks in mainstream