Caffeinated VS manifold

I'm going to be a bit blunt here, but I think there's a pretty big issue with simply a lack of experience on your part. What your proposing, these caf files, are the SOURCE of your program. Code gets changed. How on earth would your tool be useful if you only ever use it to one-off generate stuff and check in the resulting Java code? I can generate POJOs with my IDE just fine.

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...