This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-04
Channels
- # architecture (5)
- # aws (11)
- # aws-lambda (1)
- # beginners (108)
- # boot (11)
- # cider (37)
- # clara (19)
- # cljsrn (72)
- # clojure (170)
- # clojure-austin (2)
- # clojure-dev (1)
- # clojure-dusseldorf (2)
- # clojure-italy (1)
- # clojure-spec (41)
- # clojure-uk (24)
- # clojurescript (113)
- # component (2)
- # core-async (29)
- # cursive (9)
- # data-science (5)
- # datomic (72)
- # docs (23)
- # duct (61)
- # editors (1)
- # emacs (1)
- # events (5)
- # fulcro (77)
- # graphql (2)
- # hoplon (4)
- # jobs (3)
- # jobs-discuss (16)
- # leiningen (5)
- # off-topic (94)
- # onyx (37)
- # precept (5)
- # re-frame (17)
- # reagent (11)
- # shadow-cljs (18)
- # spacemacs (107)
- # specter (3)
- # unrepl (64)
- # yada (1)
Yeah, it keeps reminding me but I don't want to deal with the aftermath. I always back up my entire /etc/apache2
config beforehand -- Apple upgrades always trash that.
puts on tin foil hat it's all just a huge conspiracy by AWS/Google/MS to make people buy more cloud capacity to make up for the fact that all their intel-based servers will now be running 30% slower
at least w/cloud I can be happy that I don't own a massive fleet of vulnerable servers
Morning all đź‘‹
I feel like I've been hiding under a rock. Is there an article I can read somewhere about the doomed computers?
hi, has anyone started using tools.deps.alpha in anger?
Yeah, it keeps reminding me but I don't want to deal with the aftermath. I always back up my entire /etc/apache2
config beforehand -- Apple upgrades always trash that.
@elise_huard I wouldn't say "in anger" but I built boot-tools-deps
as a Boot task to leverage the tools.deps
library.
@seancorfield thank you - and have you been able to use it on new projects?
With some caveats, yes. Zach Oakes opened an issue about transitive dependencies not being scoped and Alex Miller responded that scopes were not supported by tools.deps
and not really supported by the Maven API either (it has phases and rules, apparently).
We haven't yet switched our build system at work over to tools.deps
but we're looking at it.
nice, might give it a go for new code then!
I was wondering, does anyone have a favoured tool for planning a data model / domain, or does everyone just dive in and start writing Spec and / or things like JSONSchema?
I am suffering a little bit of re-entry shock and also a rather towering task of planning a large data domain, in an open-ended a way as possible, for a domain that is definitely going to be multi-paradigm, i.e. RDBMS and DocumentDB / NoSQL and possibly Graphs as well (I am hoping Datomic will feature too)… I have that “so many things, so many things!” paralysis, but I do think that I can start on one of the DocumentDB areas straight away, but I would love a friendlier approach than I start hand-balling JSON…