These arguments (for any language) are pretty lacking. That you can do it isn't important - the majority culture is the deciding factor - since every internet resource, every package, every support forum is going to follow the majority culture. So not following it simply adds friction. It makes way more sense to choose something where the majority culture makes sense for you, assuming it exists.
That's very far from what I see in practice. Apart from EF, I haven't really experienced any library which forces any of the listed things on you. You can choose some framework if you want of course. But it's trivial to stay away from those.
Comments
These arguments (for any language) are pretty lacking. That you can do it isn't important - the majority culture is the deciding factor - since every internet resource, every package, every support forum is going to follow the majority culture. So not following it simply adds friction. It makes way more sense to choose something where the majority culture makes sense for you, assuming it exists.
That's very far from what I see in practice. Apart from EF, I haven't really experienced any library which forces any of the listed things on you. You can choose some framework if you want of course. But it's trivial to stay away from those.
Both Quarkus and JOOQ are pretty good in the Java world. No ORM, no inheritance etc to create APIs... Typed API clients generated for your frontend...