@Neobii, re Three.js - it's the bees knees. The Famous GL stuff would never have reached that level. There's some discussion now for infamous to use ThreeJS for the fork, with a famous'ish API... this could be pretty awesome. (Disclaimer: I have very little GL experience personally but I do read :)).
@PEM-- , yeah, it's a great pity, but if nothing else, they did show us what's possible. The discussion now in the infamous channel is quite inspiring!
@talves, will be very happy to discuss (we'll chat more in private or in infamous group). Basic idea is just to mess around first as an experiment.. I'm a stickler for performance and good design so I'm actually excited to give it a bash, but don't at this stage want to pre-commit to anything big :)
famous-views in general shouldn't have very big requirements. it's pretty big now but that was mostly to deal with inadequacies in famous. i think a lot of famous-views stuff is better suited for the engine level, and that it should be super easy to write integrations for e.g. blaze (meteor), react, angular, etc, with a similar structure. these integrations should be fairly thin, simply making sensible use of the engine API.
very happy with ES6 base, babel, npm, etc :)
blaze (meteor), react, angular, etc, with a similar structure. these integrations should be fairly thin, simply making sensible use of the engine API.
That's what I was thinking too, but it's a lot more work to go and make each integration afterwords. React, on the other hand (especially now that it's officially supported by Meteor) is looking really nice. You guys (cc @talves) should experiment with react-famous a little if you haven't yet. It's really nice (try my fork for now, at npmjs.com/reacfamo, with plans to merge with @pilwon when ready).
disappointing really, i can't find any alternatives to using famous
A lot of us felt the same way and there is some really interesting stuff happening in https://gitter.im/infamous/engine! So don't dispare yet :>
@trusktr, re integrations/react, I think the main thing is to not force something on users. We can provide an official react integration, that we support. That level of abstraction will mean that anyone else who is keen can quickly copy that code and create an integration layer for framework of their choice.