> "...the design of LINQ query comprehensions was heavily influenced by the design of Haskell. Haskell expert Erik Meijer was on the C# language design committee when we designed LINQ; his insights were very valuable".
I'd also check out a new trend in APIs that is sort of "visual editors for non-coders". Slack's Block Builder is a terrific example
Most Java OSS library feels a lot better than NodeJS (been in JS land for more than 5 years and I can count "historically" stable JS library using my left hand)
First of all, I'm talking about OSS library as API not REST endpoint so I believe your statement is totally unrelated to my point.
Second, you don't need a PhD in DAO, it's just one simple pattern.
Third, you have a few options: have your JPA entity converted to JAXB-annotated java-class using Dozer (if it's a straight up mapping, you don't need XML). Or annotate your model with JPA and JAXB. Again, this is only if you use JPA which is heavily geared toward RDBMS. If you followed NodeJS "pattern" which implies the only arsenal is MongoDB... then it's a different story. Most projects that use MongoDB has simple(ish) data structure so you probably don't need to deal with DAO and whatnot.
Fourth, I can understand your statement coming from NodeJS since NodeJS doesn't even have a good ORM that can managed different DB providers. Specific vs Battle-hardened for years => design trade-offs. Heck, NodeJS forces you to choose a specific DB drivers...
Every function came in multiple varieties, specialized for the expected and desired cache hotness of the data. Suppose you wanted to multiply a couple matrices. There are two inputs and an output. The inputs could be cached, uncached, or one of each. The output might be needed soon, and thus should remain in cache, or it might be better to save the cache for other things. All of this could be specified.
That library could help a programmer to produce mighty fast programs.
Thank you based Mapbox Unity team.
So I would imagine it would be a time (battle?) tested, mature api.