Why I Switched from Python to Clojure (2016)

Re:Why I Switched from Python to Clojure (2016) by bitwize on Sunday March 24, 2019 @08:41PM (#19479577)

Clojure lets you leverage the entire Java library ecosystem, which is flippin' huge -- bigger, even, than Python's.

[ Parent | on HN ]

Re:Why I Switched from Python to Clojure (2016) by scottlocklin on Sunday March 24, 2019 @08:50PM (#19479601)

Except for numerics, which is my whole world, where Java is horrific roadkill. FWIIW back 8 years ago I was ---><--- this close to trying to build out an important system with wrapped Fortran in Clojure. People (who even then looked like they didn't know what they were talking about) assured me the JVM would eventually surpass lapack, because MUH JVM, and that has failed to come to pass.

[ Parent | on HN ]

Re:Why I Switched from Python to Clojure (2016) by Stubb on Monday March 25, 2019 @09:10AM (#19482142)

The SciPy stack got me into Python and it making it hard to leave despite becoming 100% fed up with Python's GIL. I need to port some signal processing code I prototyped in Python to Java for a customer, and a survey of libraries for Java is not making me look forward to this effort.

[ Parent | on HN ]

Re:Why I Switched from Python to Clojure (2016) by fulafel on Monday March 25, 2019 @02:29AM (#19480663)

I'd say Clojure has just the right amount of syntactic friction to calling into java, that encourages people to write Clojurey libraries (or wrappers for Java libs) and keep the Javaisms at bay from your code.

[ Parent | on HN ]

Re:Why I Switched from Python to Clojure (2016) by AdieuToLogic on Monday March 25, 2019 @02:33AM (#19480676)

Regarding what is available in the Java/JVM ecosystem, here are some Maven Central stats[0]:

  Total number of artifacts indexed (GAV): 3,566,566
  Total number of unique artifacts indexed (GA): 272,507

0 - https://search.maven.org/stats

[ Parent | on HN ]