Forking Firefox.. That would be for sure a hell of a future Work. Independently developing/implement Features, the UI, Security patches.... Sure, something like that COULD be done - just take a look at smaller browsers like Midori or Qupzilla - they have quite a small developer team behind them, but do not forget, that that would really be a giant job then which the future fork developer would have in the near future.... I do not expect to see something like that to happen. And such a job could also not be done without the help of countless numbers of volunteers which help with the beta testing and developement/Implementing features processaccess2godzilla wrote:Somebody needs to fork FF, since "[the beast has] become hideous and twisted". Restoring core features like these simply can't be reversed in PM due to its low following, since all extensions are targeted for FF (which will have to be rewritten in inferior methods, like Noscript is doing after the removal of CAPS).
Maybe eventually we'll be informed that Mozilla is switching to the Chrome codebase.
And about adopting the Blink Engine into Firefox... While there is a chance that that could happen in the future i guess it would be highly depending if Mozilla would seriously sacrifice that large amount of time and money to develope their own Future Engine Project Servo into a fully finished product.
If they would decide to abandon that project and Gecko would reach limitations which could not be overcome anymore (Opera with Presto did reach both points already so they switched engines) then i would make a bet that Mozilla would do something like that. At least adopting Blink would save them quite much time and money because many others do already most of the work.