2 ms·
> The difference is that I have to read a bunch of documentation to understand the bean mapper, but I already know how to write java. I think this is spot-on,
by brundolf 7y ago
> The difference is that I have to read a bunch of documentation to understand the bean mapper, but I already know how to write java.
I think this is spot-on, and sums up one of my points in a way that's a bit closer to the heart of the issue. However:
> At the end of the day, library vs framework boils down to imperative vs declarative.
I don't think this is true at all. There's a correlation, maybe. Particularly in languages like Java that don't have great support for declarative stuff themselves, frameworks like Spring have served as a kind of workaround for that shortcoming. But if anything I would say pure functions lend themselves even more to library-thinking than imperative code does.