TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

How Famo.us Refused to Admit They Could Not Achieve Native Rendering After All

5 pointsby faceyspaceyover 8 years ago

2 comments

faceyspaceyover 8 years ago
In short, it&#x27;s my opinion Famo.us decided to start an agency that utilizes a sub-set of the features they developed because they realized full on applications could not be developed with Famo.us. Why else would you start an agency using what you developed? I feel it&#x27;s baloney that they purport anything else rather than tell us the truth that their assumptions were flawed. The browser simply can&#x27;t render real applications as if they are game-worlds. Not with new data constantly triggering re-renderings over the wire. Who&#x27;s ever seen anything more than a static example of famo.us? The problems were likely many though--Steve had had them do too much and change directions every other week, and as a result the offering they did provide was never complete and always full of bugs. Perhaps if they focused on a more narrow use case, they could have released their offering (and stood by it) with a straight face. For what the expectations were, the browser can&#x27;t deliver, or some other company (Google, Facebook) would attempt this by now. The idea has been out in the open for 4 years. If it was truly possible to make as reliable of an application framework as React backed by all these hardware accelerated animated views, someone would do it.<p>Now would be a good time to hear from the community developers still supporting the remains of the Famo.us framework. Can it do what we expected it could do or is it flawed? If it&#x27;s not flawed, why don&#x27;t we ever hear from you guys on hacker news, echo js, etc?? I think if it was working well, we&#x27;d be hearing as much about it as we hear about React. The shit don&#x27;t work. Don&#x27;t rely on it to build anything substantial.
cocktailpeanutsover 8 years ago
There are many reasons why they failed, but I think the main one is because they literally didn&#x27;t let people use it.<p>I don&#x27;t even know why (Probably a combination of the technology far from being ready, and their foolish idea that keeping the exclusivity will hype it up and get more traction).<p>From what I&#x27;ve seen, these developer oriented projects only succeed by working their own way up to the top instead of trying to use gimmicks like this to gain traction.