miniserde VS manifold

It's pretty common to avoid macros as they can seem too magical a lot of the time. And with traits, there's experiments like miniserde which specifically avoid monomorphization overhead. I also see people who want to avoid having lots of dependencies relatively often.

Right now, the next step would be to try to reimplement miniserde with venial, and publish benchmarks.

The only downside is compile time bloat.

Serde generates heaps and heaps of generic code. This gets optimized away to be very efficient, but it can be quite cumbersome.

Ever tried working on a crate with hundreds or thousands of de/serializable types? Compile times shoot through the roof really quickly.

The maintainer of serde also created `miniserde` [1], which uses dynamic dispatch and can have 4x compile time improvements.

Due to Rusts lack of orphan instances you really depend on a pervasive standard for serializiation which is used by all libraries, so the ecosystem is really locked in to serde by now.

[1] https://github.com/dtolnay/miniserde

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