News for hackers. Stuff that matters.
Re:A History of Clojure [pdf] by airstrike on Thursday June 04, 2020 @02:36PM (#23420134)
> Python does the same thing but with C

Don't think that's really accurate.

You don't have to use C with Python, and there's no VM to worry about. CPython* just happens to be the most popular implementation.

Clojure (by and large)* requires the whole Java infrastructure, and that is a nonstarter for many.

Re:A History of Clojure [pdf] by jdminhbg on Thursday June 04, 2020 @02:41PM (#23420195)
> Clojure requires the whole Java infrastructure, and that is a nonstarter for many.

There are Clojure implementations that run on JS runtimes, the .Net CLR, the Erlang BEAM runtime, etc.

Re:A History of Clojure [pdf] by sitkack on Thursday June 04, 2020 @07:27PM (#23423233)
Re:A History of Clojure [pdf] by roguas on Tuesday June 09, 2020 @12:33PM (#23468084)
It requires jvm. But you don't have to interact with java, sometimes its easier to just use a particular java library, but many people report never having to touch java. JVM seems like a nice to have, a lot of the standard java tooling works for clojure as well (profilers and what not).
Re:A History of Clojure [pdf] by lvh on Thursday June 04, 2020 @03:37PM (#23420831)
Nit: CPython, not Cython. Cython is a whole different thing that leverages CPython to compile Python programs to C, as well as compile Cython-the-language, effectively annotated Python, to faster C.

CPython comes with its own VM: are you saying the issue is "you need to install 2 things instead of 1"?