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 your own in the same breath is simply poor taste.
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.
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 your own in the same breath is simply poor taste.