Earlier quoted context omitted.
FWIW, preserve-3D is not yet supported in IE11, even after the Windows 8.1 update. AFAIK there is no clear ETA on when preserve-3d support will land in Internet Explorer. My best guess would be in IE12. That being said, Famo.us currently works best on mobile devices, which nets you all of the iOS ecosystem and large portions of the Android ecosystem. Is it everyone? No. Is it a big market? Yes. Will it get bigger? Ye…
It might work "best" on mobile devices, but I'm afraid that "best" is still pretty awful. In Chrome on a Moto G the frontpage gets maybe 5fps when scrolling. And not even consistently, but with seemingly random intervals between refreshes. The effect is physically nauseating, a bit like bad VR. On the same phone with Firefox it's even worse. The touch response is just so badly off that I can't even come up with a men…
Famo.us open to everyone
51–60 of 144 posts
Re: Famo.us open to everyone
#52I got a look at this during the "Secret Beta". All in all, cool idea with using the 3d matrix transform, felt very unfinished though. I also felt that the coding style was very verbose with plenty of needless inheritance tricks, etc. They have a huge physics library and a bunch of other stuff that is not necessary for 99% of apps. There was one demo for a basic app, and like 100 demos of various bouncing balls and sp…
As an employee I have mixed feelings here. For a long time (I've been with the company for 2 years), I was the main person at the company arguing for the basics necessary for all apps like you suggest we should have done. However, looking at this from the inside my view has changed to where the approach we're taking probably makes the most sense long term even though it may not be immediately obvious. First, the goal…
Well you did hype it quite a bit. Just pretend the "hate" is HN hazing for your launch; it's a bit of trend around these parts.
I have a question: is the Lumosity iOS app built on Famo.us?
Re: Famo.us open to everyone
#53Earlier quoted context omitted.
Try grabbing the scroll bar with your mouse and pulling it down the page. Nope, apparently scrollbars aren't for that. This doesn't seem to be designed with regular desktop usage in mind.
I don't know why but it seems to be perfectly acceptable to break the scrollbar these days.
Re: Famo.us open to everyone
#54Earlier quoted context omitted.
It might work "best" on mobile devices, but I'm afraid that "best" is still pretty awful. In Chrome on a Moto G the frontpage gets maybe 5fps when scrolling. And not even consistently, but with seemingly random intervals between refreshes. The effect is physically nauseating, a bit like bad VR. On the same phone with Firefox it's even worse. The touch response is just so badly off that I can't even come up with a men…
Thanks for the feedback. Out of curiosity, what version of Android are you running on the Moto G?
Re: Famo.us open to everyone
#55Earlier quoted context omitted.
I find myself agreeing with most of what you wrote, and yet, it doesn't matter. You keep sabotaging yourselves. Does no-one do QA? Do you not have a Steve Jobs-esque character who has taste and an eye for detail and who can look at this stuff the way your users will? Because such a person would've looked at this and Noped the fuck out of there, cancelled whatever PR you had planned, and put everyone around a table sa…
What's the lesser of two evils? 1) Launch an imperfect product that works well for some use cases; or 2) Perfect everything and be ridiculed as vaporware I wish we were Apple and had $159 billion in cash reserves. We're not though and have to operate within different constraints that don't afford us the same luxuries. You can't really compare Apples to Famo.uses
Re: Famo.us open to everyone
#56I'm back to using the browser like it should be (with a bit of angular on top)
Re: Famo.us open to everyone
#57Earlier quoted context omitted.
> No, we've got a ways to go. However for mobile devices, I would argue that Famo.us is definitely already there. Looking at it on Chrome in Galaxy Note 3 with KitKat, no, you aren't "already there". Scrolling is painfully erratic. And if you really want to be "mobile first", which makes sense, it would probably be a good idea to have content which (a) scaled to the width of the device, or (b) failing to scale to dev…
FWIW, KitKat isn't on the list of versions we support. We target Ice Cream Sandwich and above. Also, are you using the stock Android browser or did you install Chrome? The problem isn't with that device isn't Famo.us, and IIRC it's not the hardware either, it's the implementation of the APIs we rely on in the browser. Many people replace their mobile phones every 1-3 years. Now that smartphones are becoming feature p…
Since when is KitKat (4.4) not "above" Ice Cream Sandwich (4.0)?
> Also, are you using the stock Android browser or did you install Chrome?
Well, I said Chrome, but the problems (at least, the ones listed in my previous post) are identical in the stock browser.
> Many people replace their mobile phones every 1-3 years.
Well, yeah, I just replaced my long-in-the-tooth iPhone 4 with a still-top-of-the-line Galaxy Note 3 (though the GNote 4 will be out fairly soon.) That's the phone we're talking about here.
> Now that smartphones are becoming feature phones and all these phones have the most recent versions of Android, it's only a matter of time.
But KitKat is the most recent version of Android, and you just said you don't support it.
Re: Famo.us open to everyone
#58Earlier quoted context omitted.
> No, we've got a ways to go. However for mobile devices, I would argue that Famo.us is definitely already there. Looking at it on Chrome in Galaxy Note 3 with KitKat, no, you aren't "already there". Scrolling is painfully erratic. And if you really want to be "mobile first", which makes sense, it would probably be a good idea to have content which (a) scaled to the width of the device, or (b) failing to scale to dev…
FWIW, KitKat isn't on the list of versions we support. We target Ice Cream Sandwich and above. Also, are you using the stock Android browser or did you install Chrome? The problem isn't with that device isn't Famo.us, and IIRC it's not the hardware either, it's the implementation of the APIs we rely on in the browser. Many people replace their mobile phones every 1-3 years. Now that smartphones are becoming feature p…
Re: Famo.us open to everyone
#59Earlier quoted context omitted.
I find myself agreeing with most of what you wrote, and yet, it doesn't matter. You keep sabotaging yourselves. Does no-one do QA? Do you not have a Steve Jobs-esque character who has taste and an eye for detail and who can look at this stuff the way your users will? Because such a person would've looked at this and Noped the fuck out of there, cancelled whatever PR you had planned, and put everyone around a table sa…
What's the lesser of two evils? 1) Launch an imperfect product that works well for some use cases; or 2) Perfect everything and be ridiculed as vaporware I wish we were Apple and had $159 billion in cash reserves. We're not though and have to operate within different constraints that don't afford us the same luxuries. You can't really compare Apples to Famo.uses
Re: Famo.us open to everyone
#60"This will allow JavaScript programs to leverage sophisticated optimizations that were previously only available to native applications written in languages like C++ or Objective-C."
Would famo.us have any utility once Apple moves to that version of WebKit?