Digital Mark λ 📚 🕹 💾 🥃 on Nostr: nprofile1q…659un nprofile1q…cp4cm nprofile1q…dl9v9 No, but all of Clojure's ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqdv9q9c6vfgw409uyv3emw53jsj0z7sr6lzdtg72yk6h9sf290ydqf659un (nprofile…59un) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqnwftuw82x04cyqua8k8w7efxchm6r76eh6hz9chuusnf4v9stzwswcp4cm (nprofile…p4cm) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq9y8xknr5twkrg2aeu6dyt9rhk5eg6punm4kl4q07pp0av8aa47es8dl9v9 (nprofile…l9v9) No, but all of Clojure's problems (and Kawa's, to a lesser extent) are from being on the JVM, and its limitations. Churning cons pairs is bad, so clj uses arrays. There's no tail-call optimization, so Clojure has non-recursive goto, Kawa has that or a slower CPS-mode that does do TCO like a real Scheme.
If I had to write to the JVM for work reasons, tho, I'd use either one (Clojure for web apps, Kawa for anything else).
If I had to write to the JVM for work reasons, tho, I'd use either one (Clojure for web apps, Kawa for anything else).