Perhaps the hardest part to understand and appreciate is the extent to which the people who should be fighting for these users aren't. The board of @mozilla has a lot to answer for, given their mission: https://www.mozilla.org/en-US/mission/ https://twitter.com/slightlylate/status/979097423510294529 …
-
Show this thread
-
I expect Mark Zuckerberg to be an absentee landlord of a growing empire...that's capitalism. But where's
@cbeard or@MitchellBaker? The future is mobile. Where-the-AF-are-you,@mozilla? We need you in this fight.6 replies 0 retweets 16 likesShow this thread -
There will be all the "you've drunk the Google kook-aid" flack on this thread. Nerp. I work places that have serious, legitimate plans to make the web something other than a desktop-only, legacy-centric OS. So I work on
@googlechrome.7 replies 0 retweets 12 likesShow this thread -
Replying to @slightlylate @googlechrome
When the mobile web is largely WebKit/Blink-centric and when few mobile users install another browser, it's a hard market to break into. When you're a comparatively small organization with a comparatively small marketing budget, how do you go about it?
1 reply 0 retweets 1 like -
Replying to @gsnedders @googlechrome
Make a thing people want. UC did this. It's neither impossible nor unlikely; but it does involve understanding those users *better*.
2 replies 0 retweets 2 likes -
Replying to @slightlylate @googlechrome
But that is not in and of itself sufficient; when browser sniffing gives users worse experiences, when websites break because of non-standard WebKit/Blink features being unsupported… features almost never make up for this.
1 reply 0 retweets 0 likes -
When fennec launched it was by far the best browser for Android. Yet even then you could feel as a user that the organization behind it didn't fully supports it's existence. Still hoping for it to turn around.
2 replies 0 retweets 4 likes -
Replying to @cramforce @gsnedders and
The first version of native Fennec was a labor of love. Small room, a few engineers, an energetic feeling that we were going to do the browser “right”.
@dougturner remembers :)2 replies 1 retweet 4 likes
BTW, it was the experience of scaling Gecko down to mobile for native Fennec that directly influenced the Servo graphics stack, which became WebRender. I wanted to use the lessons learned to rebuild the stack right :)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.