How to write Common Lisp in 2017 – an initiation manual

Re:How to write Common Lisp in 2017 – an initiation manual by kazinator on Tuesday March 28, 2017 @11:19PM (#13983090)

Clojure is tied to the Java environment. Someone who has no use for or interest in that environment has no use for Clojure.

[ Parent | on HN ]

Re:How to write Common Lisp in 2017 – an initiation manual by ethagnawl on Wednesday March 29, 2017 @12:12AM (#13983333)

> Clojure is tied to the Java environment.

I guess you're not familiar with ClojureScript and/or Clojure CLR?

[ Parent | on HN ]

Re:How to write Common Lisp in 2017 – an initiation manual by mathw on Wednesday March 29, 2017 @04:00AM (#13984246)

Last time I tried to use Clojure CLR, all the useful libraries were JVM-only because they called out to JVM libs underneath.

[ Parent | on HN ]

Re:How to write Common Lisp in 2017 – an initiation manual by 59nadir on Wednesday March 29, 2017 @03:25AM (#13984121)

That's sort of like the following:

- I don't want a door here.

- Ok, you don't like the wooden door here. You can have a plastic one or a steel door.

With CL you're not tied to _any_ platform.

[ Parent | on HN ]

Re:How to write Common Lisp in 2017 – an initiation manual by kazinator on Wednesday March 29, 2017 @12:34PM (#13987942)

"Clojure" is being used as a family name for similar, but incompatible dialects. If I were Hickey, I'd trademark it and enforce against these projects.

Look at lispm's comment: https://news.ycombinator.com/item?id=13984011

It's not just the platform libs, but the semantics of things that really should be portable.

[ Parent | on HN ]