This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-15
Channels
- # announcements (1)
- # aws (79)
- # babashka (47)
- # beginners (82)
- # calva (65)
- # cider (27)
- # cljdoc (18)
- # cljs-dev (29)
- # clojure (189)
- # clojure-dev (5)
- # clojure-europe (3)
- # clojure-italy (1)
- # clojure-madison (6)
- # clojure-nl (4)
- # clojure-spec (10)
- # clojure-uk (41)
- # clojured (3)
- # clojurescript (5)
- # clojurex (17)
- # cursive (30)
- # data-science (7)
- # datomic (17)
- # emacs (3)
- # events (6)
- # fulcro (2)
- # funcool (9)
- # graalvm (29)
- # jobs-discuss (3)
- # joker (3)
- # kaocha (6)
- # malli (5)
- # music (6)
- # off-topic (21)
- # reagent (3)
- # reitit (4)
- # rewrite-clj (8)
- # shadow-cljs (49)
- # spacemacs (7)
- # sql (23)
- # tools-deps (15)
- # vim (43)
- # xtdb (19)
Mornin'
@dharrigan Did you see next.jdbc
1.0.10 is out now?
thank you @seancorfield! 🙂
Tangentially related, but why do so many Clojure libraries seem to be v0.0.0-alpha7 or similar
That sorta grates on me too. I've not worked in an ecosystem before that has so many *-alpha of libraries
Even when those *-alpha libraries are supremely more stable than release versions in other ecosystems.
The mindset of the Clojure/core team is pretty much that version numbers don't matter because all change should be accretive or fixative and never breaking. I think that Leiningen's default of 0.1.0-SNAPSHOT for newly-generated projects also has a lot to do with it.
next.jdbc
was the first library I've worked on where the idea of a 1.0.0
release was in my mind from day one as a "gold" stable release, ready for production. No breaking changes have been made since the first beta. So future releases will likely be 1.0.nnn for as far as I can imagine.
Perhaps eventually 1.1.0 will drop support for Clojure 1.10 whenever Clojure 1.X is popular enough (and 1.10 usage has dropped to almost zero).
For a long time there was a sense (in the Clojure community) that 1.0.0 was "special" and so all libraries should start at 0.0.1 or 0.1.0 and carefully work their way up to 1.0.0 but that seems to have evaporated...
(by contrast, next.jdbc
's first public release of any sort was 1.0.0-alpha1 🙂 )
(anyways, to bed in California... chat again in seven or eight hours!)
morning
Morning
Does anyone know of a clojure wrapper to the java.nio.file API? Specifically wanting support for the FileSystem abstraction… I’ve tried datoteka and it only works with Path objects on the local file system and not in other FileSystemProvider’s 😞 I’m finding I’m slowly writing my own, and I feel like someone somewhere will have done this before.
an additional complication/annoyance is that it’s built with newer java features, e.g. variable arity methods, Enum types and java streams — the interop is still pretty straightforward; there’s just quite a bit more boilerplate in clojure than with older java libraries.
are we going to the pub on the evening of reclojure?
(hoping that's a silly question)
Basically, since this is put together quickly, then anything (within reason) that can increase community strength on that day is great!
It can be announced during the day that if anyone is interestd, for people to wander to a local pub.
Now, I'm totally 100% not familiar with the area, so maybe people might know a good place to go. <shrug>
This one seems on the bigger side: https://g.page/thegreenclerkenwell?share
There are two pubs within 10 seconds walk from the crypt
I recall The Crown being the pub we used to go to after events at the Crypt. Ironically it used to be the pub we went after an event at SkillsMatter (when they had their first office) https://www.thecrowntavernec1.co.uk/
I must say, I'm playing around with clojurescript using ant design (https://ant.design/) and the wrapper (ant-man) and I'm really liking it
Looks interesting. Do you have any code your willing to share (I promise to be nice about your code)
looks good!
great work!