4 ms·
Tempting to interpret this as the last major issue in Clojure use (error messages) being resolved with the introduction of spec. Consensus on concerns seem to b
by roenxi 8y ago
Tempting to interpret this as the last major issue in Clojure use (error messages) being resolved with the introduction of spec. Consensus on concerns seem to be dissolving away from runtime issues to softer community management issues ("documentation", which is very context specific, and "startup time" which is important but precisely not an issue while running Clojure).
I do suspect that the survey is under-weighting how much beginners must struggle to navigate setting up CLASSPATH. If you don't come to Clojure from Java then the toolchain is a bit intimidating with whatever a Maven is, followed by a process of trying to follow what both Java and Clojure tools are doing. This is one area Clojure compares very poorly with, eg, C (similarly awful setup process, but usually all the burden is shouldered by the distribution provider) or Python (use pip).
It is interesting coming at Clojure from a Debian background at how resistant Leiningen has been to being integrated into the Debian apt archive. I think the package was removed in 2014 and only came back in 2018; so still isn't in the most recent stable. Given that Leiningen is itself probably the first choice of tool to manage dependencies, this raises questions about the technical underbelly of the tools used to build Clojure programs.
- mullr 8y ago> I do suspect that the survey is under-weighting how much beginners must struggle to navigate setting up CLASSPATH. If you don't come to Clojure from Java then the toolchain is a bit intimidating with whatever a Maven is, followed by a process of trying to follow what both Java and Clojure tools are doing. This is one area Clojure compares very poorly with, eg, C (similarly awful setup process, but usually all the burden is shouldered by the distribution provider) or Python (use pip). The Clojure answer is similar to the python one: use lein. This basically solves all classpath issues. In the 3 years I used Clojure professionally, there were only small handful of times I had to deal with the classpath directly, and that was only for pretty exotic packaging issues. > It is interesting coming at Clojure from a Debian background at how resistant Leiningen has been to being integrated into the Debian apt archive. I think the package was removed in 2014 and only came back in 2018; so still isn't in the most recent stable. Given that Leiningen is itself probably the first choice of tool to manage dependencies, this raises questions about the technical underbelly of the tools used to build Clojure programs. What questions does it raise? Debian doesn't deal gracefully with any external dependency management systems, as far as I know.
- puredanger 8y agoThe clj tool introduced with Clojure 1.9 is designed to help with exactly this problem. https://clojure.org/guides/deps_and_cli https://clojure.org/guides/deps_and_cli
- roenxi 8y ago> The Clojure answer is similar to the python one: use lein. This basically solves all classpath issues. Most of them. I struggled a lot with the specific case of "I have jogl installed through apt and I want to use it in a Clojure lein setup". > In the 3 years I used Clojure professionally That is why I think the issue is underappreciated. Java provides a very comprehensive set of concepts to deal with making Java code run everywhere, and that sort of thing is just baggage when trying to learn a language as an amateur on one system. I expect it becomes a feature when something needs to be done professionally and platform is no longer a given. > What questions does it raise? * In a language that requires a lot of probably-new mental models to understand, how much extra burden is created if mistakes are made configuring dependency management? * Can a novice successfully identify what is going wrong if they muck up their dependencies in a 3rd party tool? * Will a novice identify that they should be using a 3rd party tool to manage their dependencies, rather than relying on other mechanisms that might be familiar to them? * Is the hosted nature of Clojure creating interesting new failure modes for novices in the build system as issues might now straddle two languages? These aren't questions that a professional would encounter, I expect being across complicated build systems is sort of how things are. But the leap from pure Clojure, having fun in the repl, to pure Clojure + a library is a very steep learning curve. The quality of the project setup has to go up a long way. At the moment, based purely on that learning curve, it must be one of the early barriers that causes beginners to drop the language. I'm surprised it doesn't get mentioned in the survey. Watching Rich's talks, I always got the impression that dependencies in general are an outstanding to-be-thought-about problem. > Debian doesn't deal gracefully with any external dependency management systems, as far as I know. External dependency management systems fail to meet Debian user's expectations of quality and stability, tyvm :). Yeah, you're right.
- deleted 8y ago[deleted]
- cmiles74 8y agoI think it is totally bizarre that the official getting started page just kind of throws a Maven invocation in, like it's no big deal. It's at the bottom of the page, but if you are going to mention additional software that needs to be installed, why not mention Leiningen instead? git clone https://github.com/clojure/clojure.git cd clojure mvn -Plocal -Dmaven.test.skip=true package https://clojure.org/guides/getting_started https://clojure.org/guides/getting_started
- puredanger 8y agoThis is not the "first step" way to get started, which is why it's at the bottom of the page. Leiningen is not any easier to install and use than what's already there at the top of the page as the recommended path.
- cmiles74 8y agoIt looks like we disagree on this. It's unclear to me why only Linux or MacOS developers should be covered by the "first step" way to getting started. In any case, why not remove the Maven example? It's weird to see Maven promoted over tools like Leiningen and Boot. In my opinion, the "first step" should cover all three operating systems as Leningen or Boot already does (and as the getting started page admits).
- puredanger 8y agoWindows clj is a work in progress and the page will be updated when it's ready. So, it will. The Maven example is a way to get a standalone local-only (spec libs included) jar. Some people do this (it seems weird to me, but people do). Leiningen and Boot are not official tools and are more than you need to get started (excepting the Windows caveat, which is a small portion of the Clojure user base that will be plugged, hopefully soon).
- ilikehurdles 8y agoBecause most development happens on Linux and MacOS systems, and most services deployed run on Linux. Even languages that make the sdk installation easy, the rest of the ecosystem of packages and tooling often considers windows a second class citizen (thinking here of node.js and ruby at least). If you have limited resources it makes sense to target the biggest group of users first.
- billfruit 8y agoThe state of leiningen in windows itself seems to be shaky. I do feel moving away from leiningen will be better for clojure, and will provide a better "batteries included" experience for the user.