Fork me on GitHub
#portland-or
<
2015-12-21
>
mattly00:12:23

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

mattly00:12:43

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

mattly00:12:14

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

mattly00:12:36

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

mattly00:12:44

because EVERY mutation has to go through the parser

mattly00:12:52

and you can’t create one-off mutations

mattly00:12:23

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

mattly02:12:13

thinking about it a bit more,

mattly02:12:41

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

mattly02:12:58

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

jhsu22:12:17

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