Fork me on GitHub
#yada
<
2021-04-13
>
borkdude15:04:20

If you would start a new web-app nowadays, would yada still be a good choice, or do you people have other recommendations like reitit + ?x + ?y

malcolmsparks15:04:04

If you come to my clojure meetup talk tonight you'll hear my answer 🙂

borkdude15:04:41

can't make it tonight, but tl;dr: apex is ready for production? ;)

borkdude15:04:23

we are starting a new application this week ...

borkdude15:04:10

I will suggest the meetup to my colleague and invited him to Clojurians Slack / this channel

malcolmsparks19:04:58

Hope you can snag this before it disappears - otherwise the talk is online soon, but you should be able to get the gist of my points from this in a quick 60-sec skim.

malcolmsparks19:04:28

If I was doing a new application today, I'd code it in interceptor equivalents of the Ring middleware functions I've presented this evening. It depends obviously, if you know how to wield yada and don't want to learn something new, or are happy with yada's limitations, then use yada. This stuff I presented tonight is the culmination of work around apex and other libs. I think it is ready for production, if you add the security headers in Step 13.

malcolmsparks19:04:23

You can use reitit for Step 4 (locate resource) but as a router only - I don't subscribe to having different middleware on different routes as it breaks the 'uniform interface' constraint of REST.

borkdude20:04:35

@malcolmsparks Great, thank you! Should we be worried about the maintenance of yada and aleph? It's working great for us to be honest and I don't see a reason to change this, unless we need to migrate to something else because of unmaintained projects.

malcolmsparks13:04:22

yada is only getting critical fixes, at least from me - and I'm not 100% certain of the maintenance status these days of aleph. If it's working great for you I'm sure it will continue to do so - http is a slow moving tech. Presumably you are extending yada yourself for security headers, etc.

borkdude13:04:04

Makes sense. aleph has been moved to clj-commons

malcolmsparks13:04:12

Part of the reason I've been working on a new collection of projects is so that I don't make substantial changes to yada and break stuff accidentally.

borkdude13:04:15

I think we will keep using it as it's working well for us. Rewriting to something else wouldn't really justify solving a real problem that we have, even for a new similar big project.

athomasoriginal20:04:03

@malcolmsparks Just read over the above document https://www.rest.guide/README.html. Great notes and hopefully I can catch the video at some point! I’m curious about the reitit note above: are you suggesting you wouldn’t use the middleware functionality it provides, thus, opting to wrap your own?