The linked website makes my browser crash… (Firefox 31.6). I don't know what it is supposed to be but if it is a web tech, it is clearly not production ready.
It is also crashing for me with Firefox 38.0.1.
Famous Engine – JavaScript library for animations and interfaces
81–90 of 90 posts
Re: Famous Engine – JavaScript library for animations and interfaces
#82Why does this look like Three.JS code? It seems to have very similar capabilities (although Famo.us seems to have less features) and even the code seems to be familiar to me as a ThreeJS guy. Also I'd argue that ThreeJS can make for better looking results: https://clara.io/view/193070f2-e8af-4afc-a531-9d82338b5288
Code that deals with 3D space tends to look similar. Design patterns that work in such contexts tend to be common sense. Three.js can make far better looking results currently because it's a full-fledged, mature 3D engine. Famous isn't designed to compete with that. It's really intended to sort of merge DOM and 3D content so you can use both in a unified manner. Also, trashing someone else's product while plugging yo…
* Also, trashing someone else's product while plugging your own in the same breath is simply poor taste. *
Tone says a bit about people at famo.us
Re: Famous Engine – JavaScript library for animations and interfaces
#83Two out of four demos on that page don't run on IE11. And all 4 have ugly scrollbars. Nice for demos but not yet for anything real.
Re: Famous Engine – JavaScript library for animations and interfaces
#84Two out of four demos on that page don't run on IE11. And all 4 have ugly scrollbars. Nice for demos but not yet for anything real.
They all work fine on Project Spartan, which uses Microsoft's new EdgeHTML engine.
Re: Famous Engine – JavaScript library for animations and interfaces
#85Earlier quoted context omitted.
Code that deals with 3D space tends to look similar. Design patterns that work in such contexts tend to be common sense. Three.js can make far better looking results currently because it's a full-fledged, mature 3D engine. Famous isn't designed to compete with that. It's really intended to sort of merge DOM and 3D content so you can use both in a unified manner. Also, trashing someone else's product while plugging yo…
* Also, trashing someone else's product while plugging your own in the same breath is simply poor taste. * Tone says a bit about people at famo.us
I'm not an employee at Famous, nor have I ever worked for them in any capacity whatsoever.
In fact, I found Famous via working on a personal project that heavily utilized the Three.js CSS3DRenderer.
While I love Three (and by extension MrDoob) very much, the experience left me with a healthy appreciation of what the Famous team is going for. I've tried to do the very same thing myself (fuse DOM and WebGL), and quickly realized all of the pitfalls involved.
Re: Famous Engine – JavaScript library for animations and interfaces
#86Re: Famous Engine – JavaScript library for animations and interfaces
#87The bit that I find most impressive is the mixed mode demo ... http://famous.org/learn/MixedMode/index.html ... Putting an iFrame on a 3D model and still being about to use the page that's loaded is cool. The problem with that is that there are so few use cases where you'd actually want to do that.
For fun I checked out the mixed-mode demo and navigated in the inner browser to the mixed-mode demo, then within that inner-browser I navigated to mixed-mode demo again. It kinda stutters as it first loads, but otherwise seems to work great. Really interesting! Screenshot: http://i.imgur.com/ipyxFE6.png
Re: Famous Engine – JavaScript library for animations and interfaces
#88I am wondering the mobile strategy is completely abandoned because none of the examples work or look good on the iPhone. They have weird edgy / sharp borders. Didn't feel 60fps at all. Plus the mobile layout is completely broken. They seem to work fine on Macbook though. BUT the Twitter app example needs to go away. It just looks bad, OK!?
Re: Famous Engine – JavaScript library for animations and interfaces
#89The linked website makes my browser crash… (Firefox 31.6). I don't know what it is supposed to be but if it is a web tech, it is clearly not production ready.
The company I work for always only supports the latest 2 releases of firefox and chrome. I'm not arguing for or against this being production ready, but I don't think Firefox 31 support should determine whether something is production ready.
Firefix 31 is the current stable (ESR) version. Just look at how many people run it here in this thread.