Live data from Hacker News

The famo.us controversy

blog.siliconpublishing.com

31–32 of 32 posts

Re: The famo.us controversy

#31

I am perplexed. I for one am running a project that would have absolutely embraced famo.us as part of the UX. There have been lots of smoke and mirrors, a few emails dotted in to ensure we didn't think the development team had died. I smell fear here, whether it is investor fear or team fear of losing IP and control when(if) they open source the project. Whatever the issues they are harming the credibility of the pla…

Not sure if this is useful but code just check out one of the examples on codepen and click the little gear in the JS panel. They link to the famous lib there https://s3-us-west-1.amazonaws.com/demo.famo.us/befamous/fam...

Re: The famo.us controversy

#32
post #30

Ugh, this resonates with me completely. Every time I see these guys I think: Ok, I can use Greensock's TweenMax and get every single bit of performance as these dudes are getting in their crazy hyped render engine. Its just totally, completely, silly IMO -- but that said, I'm also willing to be proved wrong. (It also makes me think of Mr. Doobs Periodic table that he put out after the very first demo using the Three.…

If you've tried to use GreenSock on a mobile device, you'd see that it stutters quite a bit depending on the number and size of elements. I've tried all the famo.us demos on basic mobile phones and for the most part they all perform well in terms of fps. That is their main advantage, I think.
Post reply on HN