I expressed my BIG gratitude to London Clojurians that makes this talk happen and all who contributed to this project! As a beginner without mentor, talks like this helped me a lot! I'm excited to learn this more after mastering clojure, back& front end code stuff.
Thank you for sharing this amazing project with us. Kit really helped me understand how to effectively use integrant to build a data driven web server architecture. Cheers!
Nice! I think Clojure needs kind of reference framework as Spring for Java, Phoenix for Elixir etc.. Do you think this project could become the one for Clojure? And you talked about the architecture, could it fit with an Hexagonal Architecture? For example I would like to separate all the dependencies related to dB to the dependencies related to the events, http and so on... In java I would create for example maven submodules with different poms
Very nice project! I am sure it will be useful to all beginners (and seniors once more modules will be available). Do you have a roadmap for the libraries you want to add? Clearly everyone can contribute their own favourite but I guess having an opinionated list of modules is, kind of, expected from such a project.
Thanks, glad to hear that you like the project! We don't have any definite roadmap at the moment, but we're definitely open to suggestions from the community.
Compare something like "lein new luminus guestbook +h2 +http-kit" versus "clojure -Tnew create :template io.github.kit-clj :name eric/guestbook". I prefer that lein command. I hope you guys can make kit command-line usage simpler.
Clojure CLI being newer doesn't mean it's better. Leiningen is arguably superior for technical reasons and is more in line with the modern tooling for other languages like Rust, Elm, etc.
Is it? I mean, as a beginner, I'm confused moved and learning into new framework or just using Leiningen/old framework instead. Because, you know, the selling for "beginner friendly etc" got my attention, but I'm still comfortable with Leiningen. Hmmm, I think I need more research into this particular topic I guess.
Considering that Clojure CLI is specifically written to be better than Boot and Leiningen, using lessons learned, it probably means that it is indeed better.
I don't see how any of this is an improvement ... - for dependencies, one just takes a map of context anyway - only this makes it more confusing and elaborate, instead of setting it up manually - restarting ring handler /reloading config is not such a problem - how is business logic decoupled from IO ? was there something smart I didn't see? - you are just making a normal (auto generated, ok decent) db call in a "ring" handler ... - the config file just seems pointlessly complicated - what is it helping? It only makes it harder to change it atm based on needs - pulling in changes ex-post is quite nice, but I bet by the time I need it, it will be too different, and won't work anyway... - at 17:00 there is a bug? :address in config, but pulls :host key from config -- to me, it only shows how this weird config adds places to make silly mistakes like this, and since it will pass nil to start-server (rather than failing fast), in case it works as something you don't expect, who knows how much time one would waste looking for that bug, and would only notice in prod ... - I don't want to be an asshole - I want to be convinced that the work you put in created something amazing ... but I don't see it. Feel free to enlighten me.
I expressed my BIG gratitude to London Clojurians that makes this talk happen and all who contributed to this project!
As a beginner without mentor, talks like this helped me a lot! I'm excited to learn this more after mastering clojure, back& front end code stuff.
Thank you for sharing this amazing project with us. Kit really helped me understand how to effectively use integrant to build a data driven web server architecture. Cheers!
Nice! I think Clojure needs kind of reference framework as Spring for Java, Phoenix for Elixir etc.. Do you think this project could become the one for Clojure?
And you talked about the architecture, could it fit with an Hexagonal Architecture? For example I would like to separate all the dependencies related to dB to the dependencies related to the events, http and so on... In java I would create for example maven submodules with different poms
Love that you can add modules from the REPL!
Thanks for your work!
Very nice project! I am sure it will be useful to all beginners (and seniors once more modules will be available). Do you have a roadmap for the libraries you want to add? Clearly everyone can contribute their own favourite but I guess having an opinionated list of modules is, kind of, expected from such a project.
Thanks, glad to hear that you like the project! We don't have any definite roadmap at the moment, but we're definitely open to suggestions from the community.
How is this different than Duct ?
I'm learning Luminus at the moment, this looks cool!
Compare something like "lein new luminus guestbook +h2 +http-kit" versus "clojure -Tnew create :template io.github.kit-clj :name eric/guestbook". I prefer that lein command. I hope you guys can make kit command-line usage simpler.
Clojure CLI being newer doesn't mean it's better. Leiningen is arguably superior for technical reasons and is more in line with the modern tooling for other languages like Rust, Elm, etc.
Is it? I mean, as a beginner, I'm confused moved and learning into new framework or just using Leiningen/old framework instead. Because, you know, the selling for "beginner friendly etc" got my attention, but I'm still comfortable with Leiningen.
Hmmm, I think I need more research into this particular topic I guess.
Considering that Clojure CLI is specifically written to be better than Boot and Leiningen, using lessons learned, it probably means that it is indeed better.
the api for clojure ecosystem stuff is still so clunky. that is why clojure never really took off.
I don't see how any of this is an improvement ...
- for dependencies, one just takes a map of context anyway - only this makes it more confusing and elaborate, instead of setting it up manually
- restarting ring handler /reloading config is not such a problem
- how is business logic decoupled from IO ? was there something smart I didn't see? - you are just making a normal (auto generated, ok decent) db call in a "ring" handler ...
- the config file just seems pointlessly complicated - what is it helping? It only makes it harder to change it atm based on needs
- pulling in changes ex-post is quite nice, but I bet by the time I need it, it will be too different, and won't work anyway...
- at 17:00 there is a bug? :address in config, but pulls :host key from config -- to me, it only shows how this weird config adds places to make silly mistakes like this, and since it will pass nil to start-server (rather than failing fast), in case it works as something you don't expect, who knows how much time one would waste looking for that bug, and would only notice in prod ...
- I don't want to be an asshole - I want to be convinced that the work you put in created something amazing ... but I don't see it. Feel free to enlighten me.