magic-bean VS manifold

I like to use Magic Bean for this kind of stuff if I can't use records for some reason.

I recently stumbled upon https://github.com/bowbahdoe/magic-bean . This would be an example of solving developer needs - compatibly with the jdk way but currently ugly. Maybe we can make it nicer in the future somehow?

I think Hibernate / cases where real getters and setters are desired are the remaining usecase. The code generator I published however long ago handles specifically that boilerplate, but its Java 17+ only. https://github.com/bowbahdoe/magic-bean

For those anemic models, when they are called for (JPA) - https://github.com/bowbahdoe/magic-bean

And if you want non-magic getters and setters there is this: https://github.com/bowbahdoe/magic-bean

Considering the Amount domain types, I like the manifold project’s unit expression[1] approach where the unit and domain type are integrated and always reconciled.

1. https://github.com/manifold-systems/manifold/tree/master/man...

> I am glad to see a project that provides a robust and elegant API for building rest services in Java.

Alternatives for _consuming_ REST services is perhaps an equally interesting proposition, particularly since there are potentially potentially many consumers per service e.g., the manifold JSON project[1].

Other areas where Springboot feels overbearing include JPA/ORM support. In my view this is its greatest weakness, but like the "no one ever got fired for buying IBM" cliche, the same can be said today about Springboot.

1. https://github.com/manifold-systems/manifold/blob/master/man...