It's already established that you find $500MM reasonable. Here's a question: why invest in the next big thing while still so far behind on the last thing? Why so little investment in a solid mobile story?
-
-
Frankly, we bet the farm on mobile with Firefox OS and it failed. That was orders of magnitude more expensive than what we're doing with mixed reality. We're refocused on mobile browsers now and they will be getting much better over the next year or two.
1 reply 0 retweets 3 likes -
Why did FFOS failure mean an almost complete and total deinvestment in mobile at the time?
1 reply 0 retweets 2 likes -
Firefox OS sucked up almost all the resources Mozilla had, pulling them not just from mobile, but from desktop and web platform. No one at Mozilla was exempted from being called on to stop what they were doing to work on something for OS. It was our "mobile investment".
1 reply 0 retweets 0 likes -
This conversation started with a lot of criticism of FFOS. Yes, FFOS was a disaster. This kind of pendulum swing (BET THE FARM! NEVERMIND DEINVEST IN MOBILE!) is what's baffling
2 replies 0 retweets 0 likes -
I can't give these numbers publicly, but FxOS what not a "bet the farm" project for Moz in $. It's just the scapegoat for the current leadership. The saddest thing is that now gecko is competitive again, with no useful product to propel.
2 replies 1 retweet 4 likes -
At least 300 people worked on Firefox OS and everyone else in the technical organization was "on call". Our mobile browser team was in the single digits. Don't get me wrong, I loved Firefox OS. I worked on it and desperately wanted it to succeed. It was not a cheap failure.
1 reply 0 retweets 3 likes -
How many people are working on MR and associated projects now?
1 reply 0 retweets 0 likes -
I don't actually know. Maybe 20 or so.
2 replies 0 retweets 0 likes -
Replying to @asadotzler @wycats and
When I started contributing to MozVR it was 5 people and they were in desperate need to help; that was about a year ago.
1 reply 0 retweets 0 likes
A lot has changed in a year.
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.