Fork me on GitHub

CLJ 1.7 is still JDK 1.6 compat. right?


That’s 1.8 master snapshot still passing on three different Java 6 VMs, as well as Oracle’s Java 7 and 8.


How can I help making this page up to date


@alexmiller: I’m not writing the book, just thought maybe it’s better to get this page updated. I can build list of the books if that could help you

Alex Miller (Clojure team)03:07:00

if you have something to add, let me know. it's not intended to be "complete" as that would be quite a long list at this point


Ok. It’s really depend on what the purpose of that page. If it's there to represents how mature is the community to the outsider (somewhat similar to, I think it should have as much good books(including yours) as we know up there. Or if it serves as a reference for people who land to Clojure home page and want to get started, maybe the book like Living Clojure should be there. But yeah, it's all up to you.


I personally feeling good when finding out that book with language agnostic title such as Seven Concurrency Models in Seven Weeks covers Clojure the most. It's kind of a sign of how strong Clojure is in the concurrency area.


Anyone used Bibi buards {:get …} ? I’m getting a 404 response when I POST, was really expecting a 405.


Not the end of the world, just wonder if I’m doing something wrong


I use bidi with guards. I have not tested for 405 in this case but I suspect that just no route matches and so you end up with a 404.


Yep, think so to. Will just handle method dispatch in the handler instead (since I was already doing that). Thanks!


Yes I also do this most of the time. I use liberator for that.


Used Liberator a few times, right now I’m doing something smaller and are dispatching with the defun library


@seancorfield: Thanks. I had actually hoped that 1.8 requires Java 7 so that it can adapt some of the features.

Alex Miller (Clojure team)12:07:11

@rauh based on current plans, Clojure 1.8 will still support jdk 1.6




@alexmiller: btw, do you think it’s worth starting some public discussion about the socket repl


I’m still not clear on what the endgame for this repl is


the current specification is definitely not very tooling friendly and I really hoped that this would a viable alternative to nREPL


e.g. it’s unclear how you can do “tooling evaluation” in the scope of one connecting (things that would mess with the REPL state, like evaluating completion commands)


the use of EDN will be disastrous for clients like Emacs


as we’ll have a hard time devising an efficient EDN parser


I can’t see anything to interrupt evaluation


or obtain metadata about the state of the repl


(without doing an eval)


so, overall I’m wondering are you open to augmenting the specs


or is this something set in stone already

Alex Miller (Clojure team)13:07:34

sorry, in the middle of like 9 fires atm

Alex Miller (Clojure team)13:07:58

nothing is locked in stone about the current design

Alex Miller (Clojure team)13:07:05

and the intent is for it to be usable by tooling

Alex Miller (Clojure team)13:07:02

best place to raise issues is either on clojure-dev mailing list (prob better for design / intent) or on the ticket if specific to the patch

Alex Miller (Clojure team)13:07:25

I think that the basic notion of starting the socket server based on system properties and handing off to an accept function is solid

Alex Miller (Clojure team)13:07:47

beyond that, I've done some stuff but none of it has been reviewed yet by Rich

Alex Miller (Clojure team)13:07:27

the repl commands and the way to transmit context from one repl session to another is definitely something that is likely to evolve

Alex Miller (Clojure team)13:07:55

and I would like to hear feedback from you and Colin as to how that can be done

Alex Miller (Clojure team)14:07:15

but really clojure-dev is the best place to do that


guess I’ll write an email there to get the conversation going later today

Alex Miller (Clojure team)14:07:58

fyi, I'll be in the woods the next few days and teaching a training class the rest of the week so I will likely not be too responsive next week


I just wanted us (cider’s team) to be on your radar regarding the socket repl, because I just read that 1.8 is going to be released in November

Alex Miller (Clojure team)14:07:11

yes, now is the time to talk about it, for sure


@alexmiller: Any chance for a new core.async release? We are impatiently waiting to use offer! and poll!!

Alex Miller (Clojure team)15:07:24

Too many codes, too little time


Would be awesome to have a roadmap! It is very important library in a clojure ecosystem...


@voxdolo do you use smartparens-strict-mode? If yes, have you solved problems with evil-mode: for example when hit D or delete selection - patens become unbalanced (at the same time emacsish <c-k> works)


@nicola, probably need something like this: , works for me (well i use regular paredit though)


@robert-stuttaford: fancy seeing you here 😛