Re: What Happened to "java -jar clojure.jar hosehead.clj" ?

2018-08-02 Thread Alex Miller
Also note that if you install clj, you have everything you need to run a repl at that point - it embeds an uberjar including tools.deps.alpha, clojure, spec, and all the transitive deps needed to run clj, so there are no further downloads required (until you start using deps, which inherently r

RE: What Happened to "java -jar clojure.jar hosehead.clj" ?

2018-08-02 Thread Alex Miller
I wouldn’t rule out some sort of bundle artifact like this in the future, but the audience for this (that is not better served by installing clj) is quite small imo. That is, the audiences we are serving are something like: 1) people using Clojure for project work - need transitive dep resolut

RE: What Happened to "java -jar clojure.jar hosehead.clj" ?

2018-08-01 Thread Sean Corfield
;re not really alive." -- Margaret Atwood From: clojure@googlegroups.com on behalf of Didier Sent: Wednesday, August 1, 2018 10:08:39 PM To: Clojure Subject: RE: What Happened to "java -jar clojure.jar hosehead.clj" ? I think overall, it makes se

RE: What Happened to "java -jar clojure.jar hosehead.clj" ?

2018-08-01 Thread Didier
I think overall, it makes sense to modularize clojure. But I'm compassionate to the no internet style mindset. So I wonder if there could be a download on the clojure.org website which is an uberjar of Clojure and it's latest required dependencies? Specifically for such use case. -- You receiv

RE: What Happened to "java -jar clojure.jar hosehead.clj" ?

2018-07-30 Thread Sean Corfield
(970) FOR-SEAN -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood From: Mark Derricutt<mailto:m...@talios.com> Sent: Monday, July 30, 2018 6:48 PM To: Clojure<mailto:clojur

Re: What Happened to "java -jar clojure.jar hosehead.clj" ?

2018-07-30 Thread Mark Derricutt
On 31 Jul 2018, at 9:08, Payter Versteegen wrote: > I'd've hoped that clojure wouldn't have become as tightly-coupled with spec > (for instance), but maybe I just need to read the Rationale page more deeply. > Dependency hell blows, especially if your work environment is disconnected > from the

RE: What Happened to "java -jar clojure.jar hosehead.clj" ?

2018-07-30 Thread Sean Corfield
_ From: clojure@googlegroups.com on behalf of Payter Versteegen Sent: Monday, July 30, 2018 2:08:12 PM To: Clojure Subject: Re: What Happened to "java -jar clojure.jar hosehead.clj" ? Right, but the disadvantage is that you're releasing something that's now incomple

Re: What Happened to "java -jar clojure.jar hosehead.clj" ?

2018-07-30 Thread Payter Versteegen
Right, but the disadvantage is that you're releasing something that's now incomplete on its own. I'd've hoped that clojure wouldn't have become as tightly-coupled with spec (for instance), but maybe I just need to read the Rationale page more deeply. Dependency hell blows, especially if your wo

Re: What Happened to "java -jar clojure.jar hosehead.clj" ?

2018-07-24 Thread Alex Miller
We have begun the process of breaking Clojure into more fine-grained modules. There is no timeline for this work but we expect this to become more common in the future so we have no plans to change this aspect of packaging. The major benefit is that the modules can be released independently and

Re: What Happened to "java -jar clojure.jar hosehead.clj" ?

2018-07-24 Thread Payter Versteegen
Alex, Thanks for the links. Digging into the release notes for 1.9.0, I see that: Note that spec is in alpha state and API compatibility is not guaranteed. Also, spec and the specs for the Clojure core API are distributed as external libraries that *must be included to use Clojure*. Emphasis mi