>>105923362
>if you dont like clojure you must be a java jeet
the coping has begun.

I'll preemptively post more truthnukes about this language and its dead ecosystem

>core.async
btfo by kotlin coroutines. then btfo by java virtual threads.

>clojure.spec
somehow takes the worst of prismatic schema and malli. Retards at cognitect decided this must be a hard dependency of clojure.core itself since the 1.8.0 release. the compiler literally hard codes spec checks in macroexpansion

Rich's own "Maybe Not" talk is essentially a whole discussion of problems that malli literally solves (but I disgress, malli is useless for any static typing or compile-time guarantees. have fun with edge-cases that arent caught in production because spec checking is so dogshit slow that everyone turns it off)

>muh types bad
https://ask.clojure.org/index.php/2800/clojure-set-should-check-or-throw-on-non-set-inputs

>muh tools.deps, tools.build
Ant with s-expressions. But since its blessed by Relevance^W Cognitect, rich hickey cultists treat it as some breakthrough in build systems

inb4 you pretend Leiningen is any better

>muh test.check
half-baked implementation of shit Haskell has had for decades

>muh datomic
the only database where swapping two :where clauses turns a 10ms query into a 10s query

>muh babashka
an interpreter that barely implements half the core language and resorts to literal binary blobs for extension (see: pods). installed on maybe 2 computers in the world, 1 of which is borkdude's macbook