This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-19
Channels
- # aleph (8)
- # announcements (43)
- # babashka (43)
- # beginners (62)
- # calva (8)
- # cider (27)
- # clj-kondo (18)
- # cljs-dev (25)
- # cljsrn (16)
- # clojure (51)
- # clojure-europe (6)
- # clojure-nl (14)
- # clojure-spec (7)
- # clojure-uk (39)
- # clojurescript (17)
- # cursive (9)
- # datascript (12)
- # datomic (16)
- # events (1)
- # fulcro (7)
- # funcool (1)
- # graalvm (2)
- # graphql (5)
- # jobs (1)
- # juxt (6)
- # kaocha (9)
- # leiningen (11)
- # luminus (1)
- # malli (1)
- # off-topic (80)
- # other-languages (2)
- # overtone (3)
- # pedestal (5)
- # quil (1)
- # re-frame (6)
- # reagent (1)
- # reitit (4)
- # rewrite-clj (5)
- # shadow-cljs (207)
- # spacemacs (1)
- # specter (4)
- # sql (1)
- # vim (14)
- # xtdb (7)
https://medium.com/@benbjohnson/standard-package-layout-7cdbc8391fc1 this is a novel idea
@dominicm I say ahead because it appears we embrace event oriented systems without a blink of an eye. More update in place, synchronous approaches are still the norm in other communities, be that good or bad.
måning
Picking up on yesterdays discussion of organising apps by feature (it’s what I advocate too), it’s also worth stating that API’s or libraries should typically be organised horizontally, by layer or type of thing. As a library is typically meant to be generic and cross cutting it’ll be concerned with how you do things not so much what you’re doing.
one confession though... I don't use Emacs... we all have Cursive licenses here at Avisi.
there's always time @thomas, will still be there when you finally realise the shortcomings of lesser editors
@mccraigmccraig when you say lesser editors, you are counting size in megabytes, yes?
@cfeckardt ofc, you have uncovered my guilty secret
i do agree @dharrigan - i'm recently finding myself quite tempted by the minimalist purity of vim's grammar
And ubiquity!
It’s everywhere.
I’m waiting for the Windows based Clojure developer to write code purely with copy con
vim's strengths are composability, ubiquity, ruthless efficiency and surprise?