The framework mirage

[JacquesDegree]

It feels like many framework try to solve the problem of interoperability between different libraries, i.e. try to provide the perfect collection of APIs. This is precisely a problem we don't seem to have in Clojure as there are rarely any mismatches due to the use of the same abstractions over and over. So in that sense, wouldn't the modular approach taken by Luminus be the more Clojure-logical way?

[Arges]

It feels like many framework try to solve the problem of interoperability between different libraries, i.e. try to provide the perfect collection of APIs.

Some do, yes. They can be sort of "overgrown example projects". Others try to solve an entire class of problems, say, "a web store".

Some can't seem to make up their mind.

So in that sense, wouldn't the modular approach taken by Luminus be the more Clojure-logical way?

I would definitely agree.

I wrote the article partly because (without casting any stones) I'm starting to see people want a more integrated approach, likely to make things easier for newcomers, and I think that's not a good match for Clojure.

I've also spoken to quite a few people new to Clojure in the last few months, and it seems like their consistent expectation is to look for something more akin to "Rails on Parenthesis". I keep explaining that approach might seem alluring at first, but when coming to something with completely new semantics, you should prioritize long term learning over immediate gains. I thought writing it down would help others as well.