stuartmorgan

7 ms·

1. 1.▲
   by stuartmorgan 13y ago

   http://caminobrowser.org/blog/2011/#mozembedding Opera has a paid staff of full-time engineers, which makes rewriting a browser on top of a new engine a lot more feasible. You're right in that if Camino had the developer time it had in it
2. 2.▲
   by stuartmorgan 13y ago

   XUL was only part of the problem. Camino's goal was to make a browser that was designed for the Mac. Firefox's goal (once running on the Mac was added after the fact) was to make a cross platform browser that ran on the Mac. That's not just
3. 3.▲
   by stuartmorgan 13y ago

   There have been two attempts that I know of (and probably more) to add keychain support to Firefox, once leveraging Camino’s code. The problem wasn't technical, but resistance from Firefox leadership to the idea. IIRC they were concerned ab
4. 4.▲
   by stuartmorgan 13y ago

   Camino has been open source and developed entirely by a community of volunteers for most of its life. There were extensive instructions on getting involved on the website for many years. There was even a specific push to recruit new people