compojure-api

* Hiccup (https://github.com/weavejester/hiccup) - DSL for generating html. You can easily mix it with other language constructs. There are similar libraries for Common Lisp and Scheme. * Compojure-api (https://github.com/metosin/compojure-api) - for building web applications. Mix json-like, hiccup and clojure constructs for web applications and autogenerate Swagger documentation. * LOL book (https://letoverlambda.com/). Extreme examples what you can do with macros and code modifications during compile time. * Seesaw (https://gist.github.com/daveray/1441520) - library for building GUI apps with Clojure and Swing. Express GUI elements through declarative syntax. Qt and other libraries has similar feature, but is usually preprocessed with external tools. * Scheme - MiniKanren (https://docs.racket-lang.org/minikanren/index.html) Most of thes

compojure-api[1] is great for building a REST API, and I really like HugSQL[2] for talking to databases. Buddy[3] is good for handling auth. [1]: https://github.com/metosin/compojure-api [2]: https://www.hugsql.org/ [3]: https://github.com/funcool/buddy

I would look to Clojure / ClojureScript. Suggest you start here https://www.braveclojure.com/foreword/ and when you feel fairly comfortable you can proceed to https://github.com/metosin/compojure-api for a solid approach to building a web API.

https://github.com/metosin/compojure-api this library uses clojure.spec with Swagger APIs to check data validity.

I'm partial to Compojure API (https://github.com/metosin/compojure-api). The thing I like about it, is at the point where I've just scaffolded a barely functional prototype, I also have a spec and interactive documentation. That documentation serves as the service's first UI. UX peeps think I am sadistic, but I like having the controls embedded in the manual. It is also very beautiful. If you look at the examples, there are few forms (keywords, in other languages) that are not related to the domain of an HTTP API. The code is dense, but rich in relevant information. If you want to explore the underlying architecture, look up the Ring project. It contains the lower level server primitives that several web frameworks are built on top of.

Do people write Swagger files by hand? That sounds awful. I was under the impression everyone used tools like I use in Clojure (compojure-api[0] and ring-swagger[1]). [0] https://github.com/metosin/compojure-api [1] https://github.com/metosin/ring-swagger

The first issue is addressed by templates. I maintain Reagent and Luminus templates and make sure that Cljs compiles correctly for both dev and prod targets. While I understand author's complaint regarding it being difficult to retrofit the template code into an existing project, I really don't see a simple solution to that. Standard behaviors can be extracted into plugins and libraries, but project specific configuration really does have to be part of the project. The Figwheel REPL can be trivially connected to an IDE as seen [here](http://www.luminusweb.net/docs/clojurescript.md#clojurescrip...). This should work with any editor the has nREPL support. There's really no good reason to use the built in REPL on the command line when you can connect the editor and send the code for evaluation directly from there. In terms of client-server i