This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-16
Channels
- # admin-announcements (14)
- # announcements (1)
- # aws (1)
- # beginners (105)
- # boot (609)
- # braid-chat (4)
- # braveandtrue (3)
- # cider (24)
- # cljs-dev (13)
- # cljsrn (2)
- # clojure (142)
- # clojure-berlin (7)
- # clojure-ireland (7)
- # clojure-japan (10)
- # clojure-nl (4)
- # clojure-poland (76)
- # clojure-russia (198)
- # clojure-sg (4)
- # clojure-taiwan (1)
- # clojurebridge (1)
- # clojured (4)
- # clojurescript (73)
- # conf-proposals (11)
- # cursive (10)
- # datomic (32)
- # devcards (1)
- # dirac (22)
- # editors (5)
- # emacs (3)
- # events (4)
- # funcool (19)
- # hoplon (18)
- # job (1)
- # jobs (3)
- # jobs-rus (16)
- # keechma (25)
- # ldnclj (33)
- # lein-figwheel (10)
- # leiningen (4)
- # luminus (1)
- # off-topic (19)
- # om (255)
- # onyx (51)
- # overtone (1)
- # parinfer (206)
- # perun (5)
- # proton (2)
- # re-frame (3)
- # reagent (2)
- # remote-jobs (13)
- # ring-swagger (7)
- # slack-help (4)
- # yada (7)
Hi, very interesting framework! I like the way handler registrations are not global, I always felt this was a little weird in re-frame.
And the entity-db stuff is very exciting too - though I dislike manually having to trigger “garbage collection”. It would be nice to make reference counting work somehow, but I guess the problem are cycles like always...
@bteuber: the nice thing about this approach is that it's easy for another controller to take a hold of an item before it's vacuumed
in the place my order example
when you go from the restaurants to the restaurant page
the restaurant controller can check if the restaurant entity is already loaded
and if it is it will return it immediately instead of making a req
regarding the automatic vacuuming of the entity db, it could be done but I don't want to add any kind of "magical" behavior to keechma
all the components are meant to be low level, so you could use them to build something more opinionated on top of them
yeah, EDB is meant to be simple, and it's purposefully not complected with the rest of the framework. If there's something that works better for your model structure, you can easily swap out the EDB
without the whole “framework” notion would be rather scary, but like that it’s more of a tool collection
Yeah the only frameworky part is the app-state lib which glues everything together. Stuart Sierra's talks (http://www.infoq.com/presentations/Clojure-Large-scale-patterns-techniques and https://vimeo.com/100978431) had a huge impact on the design
Awesome job on the docs @mihaelkonjevic
thank you I kinda feel I should rewrite them again, there's still a lot of things I want to explain
I love that you added routing, that is so important. We have very big app with re-frame bit I am definitely keeping an eye on Keechma
We have a sort of homemade entitydb
keechma actually started as Re/Frame and Secretary combination, but I didn't like the shared global state everywhere, and I wanted my controllers to be route driven so I finally bit the bullet and implemented it on my own
also, I like how controllers allow you to encapsulate both the retrieval of the data and mutations of that data too
Yes I will give it a try