Re:Camino browser reaches its end
by asperous on Friday May 31, 2013 @01:02AM
(#5796956)
My opinion is that Google/Mozila is pushing HTML5 instead of plugins not because that's what's best for the web, but because exactly this-- it decreases the potential for competition.
[ Parent
| on HN ]
If you really want to get a good conspiracy theory going, note that a lot of the main Camino people have worked at Google for many years now (longer than Chrome has existed), and the other main person went to Apple.
I think this is the first time I've ever heard anyone accuse Mozilla of stifling competition.
They must be quite bad at it, because both their browsers are split into components that can easily be reused in competing products.
The whole reason Camino has been discontinued is that the components that make it easy to reuse Gecko in their competing product were removed from Gecko.
I'd like to see your source for that claim. At first glance it seems that popularity of Camino, both among its developers and its users, has been declining for years.
A big counter-example is Opera Software switching away from their own engine to WebKit/Blink.
Re:Camino browser reaches its end
by stuartmorgan on Saturday June 01, 2013 @05:19AM
(#5803348)
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 its heyday it might have made the jump and survived, but the end of Gecko embedding is what made it impossible for Camino to continue to be maintained indefinitely by one or two people.
In what way does using HTML5 over plugins decrease the potential for competition? If anything it makes for more competition as the need for browser-specific plugins is removed.