manifold VS NodaTime

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

Surprised no one mentioned https://github.com/nodatime/nodatime

What does moment.net do better then a combination of (Humanizer)[https://github.com/Humanizr/Humanizer#humanize-datetime] and (NodaTime)[https://nodatime.org/]

.NET's DateTime isn't amazing, it's true, but I think there's been some small improvements in that area recently. If you need something more robust, you can always reach for Noda Time.

Do you .NET programmers have a moment to talk about my personal Lord and Savior NodaTime? https://nodatime.org/ There is one datetime library, and Jon Skeet is His messenger.

Timezone and language support are two different subjects. For time-related issues, Nodatime can help.

it's already been said... https://nodatime.org/

Noda time is very clean/well written IMO -> https://github.com/nodatime/nodatime