Hi, referred to here by the fine folks at #clojure-europe…

would like to say that I like the idea of yada a lots, so it is a pity to see its momentum stalled

a few things:

0) for context, https://gist.github.com/lemonteaa/7165a89442eed5c850c54934aaa01eaf this is my own analysis of the current situation of Clojure backend ecosystem

1 ) The doc is nice, but it seems to be WIP starting from about ch7 onwards ( https://www.juxt.land/yada/manual/index.html )

I do think the 6 examples listed are all great, and it can be attractive to new-comer to have just one more of them filled out in-details

maybe re-org those into its own page/highlight? (just a suggestion) (after having some forward progress)

2 ) imho, the distinguishing value of yada is its API orientation + “modernized design” (whatever that mean)

3 ) yada can be further enhanced by offering integration against recent developments of other tools/libraries…

an example: site is a specific use case web-framework/library. While working on my own poc of doing glue work on pedestal + lacinia (i.e. GraphQL) + xtdb, it comes to my attention that sth like site would help a lots to eliminate repetition…

… however, sometimes custom logic is really necessary. So an ideal situation would be using general purpose weblib, but it has the ability to integrate a site for some part of the URL routes, while falling through to custom logic for the rest

Hi @lemontea, thanks for all your points, your gist is very interesting/useful. I do have some comments but I feel I need some time to compose them properly. I'll give it some thought over the weekend. Thanks again 🙂