| > Locked out of iOS. So is Chrome, at least in the sense the iOS Chrome is slow as hell because Safari gets special privilege. But that is the case with all iOS software - you are beholden to Apple. I wouldn't consider success or failure there something you can control at all. > Under heavly competition on Android. True, but mobile FF has the best UI out of all of them, I think. > Put the metro port on the back burner. Because nobody used it. At all. It is senseless to make and maintain a product nobody will use. All this says is that Metro is systemically panned. > Increasingly fighting to stay on feature parity with Chrome on the desktop. Unless you mean things like MSE, I don't see where FF comes up short. Since version ~8 their engine has been on par or faster than Chrome and they support emerging web standards like RTC overnight. > FirefoxOS still to make an impact. It isn't targeting the first world, it will never make an impact here - it is a sound decision, it would be impossible to take Android on directly, and they really don't have to, since FF on Android has their marketplace. It is getting sizable deployment contracts in India and such, so I'd call that a success. > I wonder if there's space for Firefox. Of course. It is the only major web player pushing openness without an agenda (like Google). > It would be such a shame not to see it around 5 years from now. Even if Mozilla the company were a shell of its former self, I imagine the community would pick up a lot of the slack to keep Firefox at least usable, if not bleeding edge, like with how Thunderbird is doing. > I wonder if it makes sense for a small organization to spend so much time and money on a custom rendering engine. Is it such a horrible idea to fork and contribute to blink? Just thinking out loud. Mostly out of despair. Does it make sense to have half a dozen python interpreters? Or 3+ binary cross platform compilers? How about how many GUI toolkits are out there, from Wxwidgets and EFL to more popular cross platform ones like Qt or Mono. And they are developing Servo as the solution to Gecko being really old at this point. And Rust is an amazing language, and I'd definitely look to develop in it as soon as it hits a 1.0 (probably when Servo is ready). |
Thanks for the kind words :)
We expect Rust to be at 1.0 before Servo becomes a production browser engine.