This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-07
Channels
- # admin-announcements (4)
- # aws (2)
- # beginners (25)
- # boot (116)
- # braid-chat (4)
- # cider (6)
- # cljsjs (4)
- # cljsrn (17)
- # clojure (196)
- # clojure-austin (23)
- # clojure-belgium (5)
- # clojure-dev (78)
- # clojure-dusseldorf (6)
- # clojure-italy (2)
- # clojure-japan (6)
- # clojure-poland (1)
- # clojure-russia (132)
- # clojure-sdn (1)
- # clojure-uk (26)
- # clojurescript (87)
- # code-reviews (3)
- # core-async (26)
- # cursive (8)
- # datomic (40)
- # devcards (8)
- # emacs (4)
- # funcool (32)
- # hoplon (30)
- # jaunt (34)
- # jobs (1)
- # lein-figwheel (1)
- # leiningen (5)
- # om (14)
- # onyx (8)
- # overtone (31)
- # parinfer (14)
- # proton (8)
- # protorepl (1)
- # re-frame (30)
- # reagent (10)
- # spacemacs (2)
- # untangled (107)
- # yada (3)
@niwinz: could you please elaborate what is the reason catacumba has such small heap footptint? Is it because ratpack doing something differently than others or catacumba or both? Just curious, didn't look at it very carefully yet
I know about that but I was suprised that it works pretty well with very low memory resources
Many java applications can't use the aws micro instance bacause of memory, but for catacumba this is not a problem
forget about auth, it is brokern and legacy code that will be deleted in next versions
because it includes a lot of fixes and consistency improvements in the available impls
niwiz: thanks! I read docs on catacumba and approach looks very interesting. I'll definitely try it on some pet project.