vertx
xforms
| vertx | xforms | |
|---|---|---|
| 1 | 4 | |
| 18 | 563 | |
| - | - | |
| 0.0 | 5.4 | |
| about 2 years ago | 3 months ago | |
| Clojure | Clojure | |
| Mozilla Public License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vertx
-
Why Clojure?
There haven't really been a lot of efforts to get a high-speed web frameworks done in just Clojure as that's not normally how professional Clojure developers work and deploy code. Not a lot of Clojure developers use frameworks in the first place, so the HTTP server ends up being something that gets pulled in as a library, and since it's running on the JVM, you use JVM servers, which are fast. vertx seems to be something that scores high, but unfortunately only the Scala binding seems to be in the benchmark you mentioned. Here's a Clojure alternative: https://github.com/vertx-clojure/vertx
CLI apps are easily solved with Babashka now.
xforms
- Critique of Lazy Sequences in Clojure
-
Dealing with nested transducers ?
Maybe https://github.com/cgrand/xforms The for transducer might help, just as the for comprehension helps unpack and map/filter nested stuff.
-
What are some great Clojure libraries, as of 2021?
cgrand/xforms is a very useful hidden gem, if you like transducers/eager evaluation/solving map-vals without meander/specter.
-
Why Clojure?
* It's fast enough for 99% of apps out of the box. It's fast enough for 99.99% of the apps with minimal tuning.
* Yes, if your project is very big and macro heavy, it can take some time, but startup times have improved. In any case, I BARELY need to restart my development JVM. I have one currently running that I haven't restarted for 1 week+.
* Depending on what's your cup of tea, there's emacs/CIDER or IntelliJ/Cursive. They both work well. IntelliJ/Cursive is an excellent IDE combination. I use it every day.
* Java interop is very straightforward, not sure what you mean. Sure your code might not be all pure anymore, but that's the price for solving actual problems.
* Good java libraries have wrappers. A ton of original Clojure libraries as well. https://github.com/cgrand/xforms for example allows you to easily do things that I can't even imagine doing in an imperative language.
* Static vs dynamic typing: don't want to get into that.
* "Clojurescript isn't the same language". I use both Clojure and ClojureScript every day and as far as Clojure-only code is concerned, it works in both languages 99.99% of the time. One case you can encounter issues is if you do something host-specific, like dealing with numbers. That's by design. Clojure embraces each host, does not try to reinvent it. When you just use pure Clojure data structure manipulation, it works the same across both languages and works like magic.
What are some alternatives?
Jooby - The modular web framework for Java and Kotlin
babashka - Native, fast starting Clojure interpreter for scripting
parinfer-rust - A Rust port of parinfer.
clojure-dsl-resources - A curated list of Clojure resources for dealing with domain-specific languages.
pomegranate - A sane Clojure API for Maven Artifact Resolver + dynamic runtime modification of the classpath
meander - Tools for transparent data transformation
ghci-ng
transit-format - A data interchange format.
crux - General purpose bitemporal database for SQL, Datalog & graph queries. Backed by @juxt [Moved to: https://github.com/xtdb/xtdb]
lispy - Short and sweet LISP editing