This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (103)
- # boot (48)
- # cider (2)
- # clara (12)
- # cljsrn (9)
- # clojure (133)
- # clojure-art (3)
- # clojure-dev (9)
- # clojure-korea (7)
- # clojure-russia (228)
- # clojure-spec (8)
- # clojure-uk (26)
- # clojurescript (131)
- # cursive (8)
- # datomic (30)
- # emacs (4)
- # events (2)
- # hoplon (47)
- # lein-figwheel (5)
- # off-topic (1)
- # om (12)
- # onyx (337)
- # perun (23)
- # planck (15)
- # proton (3)
- # re-frame (5)
- # spacemacs (20)
- # untangled (97)
- # utah-clojurians (1)
- # yada (13)
@mccraigmccraig yes it... not the thing that comes after winter... or the thing where water comes out of the ground, or the thing that is in a car to make the ride more comfortable, or something else that the word spring might mean...
Afaict Spring Boot takes most of its inspiration from the (IMHO superior) Dropwizard.
i found dropwizard rather poor, when compared to similarly placed offerings from other languages
the tutorial begins with making you create a multi-module POM project with 3 sub-projects, and never explains why
what I liked was the approach of being a collection of well-regarded libraries and some optional glue code, rather than a framework
once your code gets lost deep in the spring framework it becomes like ransomware
I remember some of the defaults and choices being annoying to my preferred approaches
eg. by default the jackson deserialisation on incoming requests would explode on unknown keys - which made evolving APIs a pain
or trying to do 12-factor style environment variable overrides for config while keeping defaults in the yaml was weirdly difficult
I think generally the java community has been a little behind the curve on 12-factor - but I could be wrong about that, its a big community.
it’s the nicest java web service framework i’ve used, but didn’t feel close to something like compojure
But then again, I hadn’t done any java for a while at that point, so that was probably a factor
Yeah - dropwizard was the nicest stable java framework around, when I used it. As far as I can tell almost all strongly-typed language frameworks don’t follow Postel’s law - they just love deserialising incoming requests into objects, and throwing an error when the request has extra parameters.
presumably in languages with modern types it’s easy to say “this object should have these keys, but I don’t care if it has extra keys I’m never going to use”?
Wikipedia suggests “robustness principal” but I prefer names that make me sound authoritative 🙂
it’s not too hard to do it in jackson, i was just annoyed that it wasn’t the default, and the setting was buried in the docs