News for hackers. Stuff that matters.
Re:A History of Clojure [pdf] by zitterbewegung on Thursday June 04, 2020 @01:58PM (#23419694)
Yea Clojure is like the Python of lisp style languages. Good language design and it can interact with Existing Java libraries. (Python does the same thing but with C).
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"?

Re:A History of Clojure [pdf] by kgwgk on Thursday June 04, 2020 @02:14PM (#23419886)
Common Lisp also does the same thing with C.
Re:A History of Clojure [pdf] by mumblemumble on Thursday June 04, 2020 @02:29PM (#23420058)
And Hy does the same thing but with Python.

I think, though, that the things that Clojure gets right go way beyond just the JVM, though. Clojure's approach to nil punning, for example, is really well thought out.

Re:A History of Clojure [pdf] by jlarocco on Thursday June 04, 2020 @03:48PM (#23420941)
"nil punning" has been a feature in Lisp since the earliest days, but as far as I know it's only called "nil punning" in the Clojure community.

I don't have anything against Clojure (well, I'm a little negative on the JVM), but I personally don't see any reason to move to it from Common Lisp.

On the other hand, I'd miss CLOS, and I feel like CL has a better/more consistent design. Something about Clojure always feels like they're "winging it".

Re:A History of Clojure [pdf] by fmakunbound on Thursday June 04, 2020 @02:34PM (#23420110)
nil punning?
Re:A History of Clojure [pdf] by mumblemumble on Thursday June 04, 2020 @02:40PM (#23420181)
Eric Normand explains it better than I could: https://lispcast.com/nil-punning/

In a nutshell, nil punning is a thing in lisps (and some other languages) where the null value can have different meanings in different contexts. It's comparable to Python's concept of "truthiness" and "falsiness", but more so.

Re:A History of Clojure [pdf] by fmakunbound on Thursday June 04, 2020 @02:47PM (#23420270)
Oh that, yeah that's what I'm used to from Common Lisp as well.