@IjzerenHein, yesterday:
Hi, no official statements yet, but here is what I wrote to someone else earlier this week:
So I think that mixed mode is a big step forward. I like the API a lot better and it addresses several important things such as garbage collection and being able to define differential sizes easily, and that's a big thing. At this stage only the engine has been released, but if you want to build apps, I think we really need the new "famous platform" as well (which should contain a scrollview control), which will be available as a public beta next month.
So, I've been playing around with the new API and trying to get a good feel for it. I have a basic version of a LayoutController up & running and I will be releasing that in the near future. I'm also working on AutoLayout (cassowary constraints) as I myself have a big need to make doing layout even easier and faster.
Concerning upgrading my famous projects. Some libs that I have created try to solve a particular problem with famo.us (e.g. famous-bkimagesurface, famous-sizeconstraint). These things can now be achieved properly with famo.us itsself, so I don't intend to update those. Others, like famous-map and famous-flex, I will continue to support. My goal is to update these projects in a way so that they have an API that matches the new vanilla famo.us / framework API. I think that's important and that developers only have to learn one style of API. Because of this I'm waiting in anticipation of the famous framework and BEST. When released I will probably update my projects shortly after that. In the meantime I will be working on getting the internals ported and probably add some GL features.
Hope that gives you a glimpse of what's coming next.
This is from https://github.com/IjzerenHein/famous-flex/issues/108 - any comments should be made there - but remember, this was just an informal update and not an "official statement".
