portland-or

Clojure in PDX yo!
mattly 2015-12-21T00:49:23.000027Z

so I’ve spent some more time with om/next since the meetup on Thursday

mattly 2015-12-21T00:49:43.000028Z

and come to the conclusion that there are a lot of good ideas buried in a mess of complication

mattly 2015-12-21T00:50:14.000029Z

and while the work project on om/current would benefit from some of those ideas,

mattly 2015-12-21T00:50:36.000030Z

I’m actually concerned about how to build large apps in om/next sanely

mattly 2015-12-21T00:50:44.000031Z

because EVERY mutation has to go through the parser

mattly 2015-12-21T00:50:52.000032Z

and you can’t create one-off mutations

mattly 2015-12-21T00:51:23.000033Z

so I’m left wondering things like, is it even possible to create generic re-usable components?

mattly 2015-12-21T02:12:13.000035Z

thinking about it a bit more,

mattly 2015-12-21T02:12:41.000036Z

the big hoopla around om/next has to do with state management between data and view

mattly 2015-12-21T02:12:58.000037Z

the problem is that it’s coupling the view to the implmentation too much

2015-12-21T22:40:17.000038Z

that was my concern also, but I guess not every component needs to express its needs