keechma

Keechma stack. Mention @U050986L9 or @U2J1PHYNM if you have any questions
bteuber 2016-02-16T09:11:01.000011Z

Hi, very interesting framework! I like the way handler registrations are not global, I always felt this was a little weird in re-frame.

bteuber 2016-02-16T09:12:10.000012Z

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...

mihaelkonjevic 2016-02-16T09:50:41.000014Z

@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

mihaelkonjevic 2016-02-16T09:51:43.000015Z

in the place my order example

mihaelkonjevic 2016-02-16T09:51:53.000016Z

when you go from the restaurants to the restaurant page

mihaelkonjevic 2016-02-16T09:52:11.000017Z

the restaurant controller can check if the restaurant entity is already loaded

mihaelkonjevic 2016-02-16T09:52:29.000020Z

and if it is it will return it immediately instead of making a req

mihaelkonjevic 2016-02-16T09:52:57.000021Z

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

mihaelkonjevic 2016-02-16T09:53:23.000022Z

all the components are meant to be low level, so you could use them to build something more opinionated on top of them

bteuber 2016-02-16T09:53:52.000024Z

right I think it’s a great starting point

bteuber 2016-02-16T09:54:16.000025Z

and I’ll have to experiment more with the entity stuff in general I guess

bteuber 2016-02-16T09:54:49.000026Z

maybe I’ll find out what I want on top after a while

mihaelkonjevic 2016-02-16T09:57:06.000027Z

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

bteuber 2016-02-16T10:02:50.000029Z

yeah that’s something else I like, modularity between framework parts

bteuber 2016-02-16T10:03:08.000030Z

without the whole “framework” notion would be rather scary, but like that it’s more of a tool collection

mihaelkonjevic 2016-02-16T10:04:43.000031Z

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

bteuber 2016-02-16T10:18:10.000033Z

Thanks - I’ve seen the components talk but not the scaling one, will check it out :simple_smile:

mitchelkuijpers 2016-02-16T12:44:30.000034Z

Awesome job on the docs @mihaelkonjevic

mihaelkonjevic 2016-02-16T12:45:00.000035Z

thank you :simple_smile: I kinda feel I should rewrite them again, there's still a lot of things I want to explain

mitchelkuijpers 2016-02-16T12:45:36.000036Z

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

mitchelkuijpers 2016-02-16T12:45:56.000037Z

We have a sort of homemade entitydb

mihaelkonjevic 2016-02-16T12:46:59.000038Z

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

mihaelkonjevic 2016-02-16T12:47:42.000039Z

also, I like how controllers allow you to encapsulate both the retrieval of the data and mutations of that data too

mitchelkuijpers 2016-02-16T12:50:04.000040Z

Yes I will give it a try