Same for me, but the webpage gave the impression that it was still downloading, because after it download completely, at least in firefox on iPhone, it’s still showing that it was downloading.
In my opinion, Go is great to make REST APIs, but for full-fledged frameworks (with server-generated HTML views) Rails will always be light years ahead for the developer productivity and happiness. That's why the article focus on a web framework to make REST APIs.
That is why Go frameworks need to be made though, the process of evolution will produce varying and improved frameworks. Flotilla(https://github.com/thrisp/flotilla/tree/develop) was started bring something Flask-like to the workflow at Thrisp. Its not rails and intended to be a micro framework, but aims for full-fledged.
I like this as a concept, but I wouldn't recommend to build websites with it. I wonder how user-accessible websites built with famo.us are — for example I can't just use my arrow keys to navigate up/down and tab'ing through elements does not move the scroll-bar accordingly, this could be an issue for some, older internet users.
You can build that functionality if it's really a problem. Also surfaces within Famo.us afaik are just like normal sections on a webpage where your normal tabbing and arrow keys will work.
But if you're building more traditional looking web apps in famo.us, I don't think you'll run into the issues you're talking about.
