[AdrianRossouw]

So famo.us has got a pretty bad reputation, but it's actually a really good idea.

The code is actually really well written too, and I'm sure that any bugs it has.. vis a vis scrolling etc.. are not design faults. They can be fixed.

This is probably the best technical explanation I have seen of what famo.us actually is :

http://ibm.com/developerworks/library/wa-famous/index.html

[argonaut]

I don't get the hate famo.us gets on HN. But to be clear, their code isn't the best. Their code is quite janky in places and is very poorly documented (in the source and in the docs). I'm also pretty sure the bugs it has are design faults. All of this can be fixed, though, which is why I like to take a "wait and see" approach with famous.

[malandrew]

While we're aware of some design issues that we're currently working on addressing, we'd still love to hear what you think are famo.us' current design flaws and how you think things should be implemented differently.

[XaspR8d]

Wrong thread? Or do you know something we don't about Frame.io's choice of interaction framework? :)

[johntraver]

Yea looks like the title got edited. This Signup page is built in Famo.us