I didn't even know this existed until this post happened.
Camino browser reaches its end
31–40 of 127 posts
Re: Camino browser reaches its end
#32A shame the energy that went into Camino didn't go into MacFirefox.
It seems like XUL required ten times as much effort to get comparable results.
Re: Camino browser reaches its end
#33Unfortunately/fortunately with browsers becoming more of an OS replacement, it makes it rather hard if not impossible for small teams to maintain them.
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.
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.
Re: Camino browser reaches its end
#34A sad announcement, but the writing has been on the wall for a few years now (specifically, since Mozilla officially dropped support for embedding[0]).
I'm only surprised they waited this long to make it official.
[0] https://groups.google.com/forum/#!topic/mozilla.dev.embeddin...
Re: Camino browser reaches its end
#35I find this extremely saddening because Camino offered the best native experience for OS X, with all the polish of a well-designed Cocoa app, on top of Gecko. I'll miss Camino.
I want to like Firefox, I really do, but the experience on OS X is awful. It doesn't fit well with the aesthetic of a native Mac app, and certainty doesn't' function like one. Multi-gestures in Safari are so much smoother. About a month or so back when the Firefox team was soliciting feedback for something here on HN, one of the designers or developers at Mozilla had screenshots of a version of Firefox that looked re…
The one thing that drives me mad about Firefox on the Mac is it's Home/End behavior. Ever since migrating to the Mac, I have remapped the keys to work like on windows and Linux (operating on the current line instead of the current document).
You can do that using a custom key binding in ~/Library/KeyBindings.
Firefox ignores this and still insists on home/end working on the full document. But even worse: in the new Gmail compose window, not even Command-Left/Right works (it does in other Textareas - no idea what Google did here).
Now this might totally be a case of http://xkcd.com/1172/ but by the life of me, I cannot work without a way to move the cursor to the beginning of a line - especially when the keys that I usually use are so destructive (scrolling all the way to the top, making me lose my position).
This is the only reason why using Firefox is out of the question.
In the past, I patched some JS file inside the bundle, but now that Firefox updates so often and it's a signed binary, I can't really do that any more.
Re: Camino browser reaches its end
#36I only stopped using Camino when I became dependent on some Firefox extensions (AdBlock, NoScript, eventually others). The big downside to Camino having a fully native UI was that it didn't have XUL support, so no cross-compatibility with FireFox extensions.
As soon as one of the Mac-compatible WebKit browsers can replicate the functionality of AdBlock Plus, NoScript, and BetterPrivacy, I'll quit using FireFox on OS X, because it's still noticeably non-native and has some persistent annoyances.
Re: Camino browser reaches its end
#37Would it be such a sin to continue to use it for a while practicing safe browsing techniques? Or am I naive to think that I can avoid being harmed browsing trusted sites with my beloved browser? Seemed to be a favorite for marketing campaigns thanks to it's minimal interface. Camino will be missed.
your primary risk would be bad networks serving up malware, which is pretty hard to defend against
Re: Camino browser reaches its end
#38I only stopped using Camino when I became dependent on some Firefox extensions (AdBlock, NoScript, eventually others). The big downside to Camino having a fully native UI was that it didn't have XUL support, so no cross-compatibility with FireFox extensions. As soon as one of the Mac-compatible WebKit browsers can replicate the functionality of AdBlock Plus, NoScript, and BetterPrivacy, I'll quit using FireFox on OS…
AdBlock Plus is available for Chrome and NotScripts replicates NoScript. I'm not sure what BetterPrivacy gets you that you can't do yourself by changing your cookie settings.
Re: Camino browser reaches its end
#39I loved Camino back in the 10.1 / 10.2 days. It was truly epic , and so much better than the god awful IE for Mac.
IE for Mac? That has to be an oxy moron of some sort.
There was an IE for UNIX back in the 1990s, which meant Solaris and HP-UX. The last version was IE5.
http://en.wikipedia.org/wiki/Internet_Explorer_for_UNIX
And before that, MicroSoft was best known for its BASIC implementation that wound up on a whole range of eight-bit microcomputers.
https://en.wikipedia.org/wiki/Microsoft_BASIC
The versions for 6502-based micros shared a codebase:
http://www.pagetable.com/?p=46
And, in some versions, they had an easter egg hidden in the constants used to implement SIN:
Re: Camino browser reaches its end
#40Earlier quoted context omitted.
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.
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.
Would you want to try to build a web browser today?
What if you only needed to implement html1.0 and NPAPI?