Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Camino browser reaches its end

caminobrowser.org

Post reply on HN
Print view View original

81–90 of 127 posts

Re: Camino browser reaches its end

#81

Post by Samuel_Michon »

gaius wrote: post #78
Samuel_Michon wrote: post #62

“Camino is not receiving security updates” “Camino reaches its end” “Camino is no longer being developed” I don’t like the tone of this press release. They make it seem like they’re not responsible for the lack of updates and that Camino died a natural death. They didn’t offer an explanation nor did they give any advance notice. Not very classy.

From http://caminobrowser.org/blog/2011/#mozembedding As a purely community-based open source project, no one is employed to work on Camino; all Camino developers are volunteers, working on Camino in their spare time, as a labor of love. While maintaining embedding in a fork of Gecko is theoretically possible, we don’t have the manpower for a sustained effort of that kind

Ah, that explains a lot. It also shows the shadow side of open source software development: if the developers get bored, they can just up and leave. If all the devs do so, the project is dead but there’s no one there to call it. Users aren’t owed any explanation.

Re: Camino browser reaches its end

#82

Post by lttlrck »

masklinn wrote: post #58
fleitz wrote: post #3

I 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.

I still love it. To this day it remains my primary browser, through its aged rendering, through its lockups on JS-heavy sites, through its dated icons, through everything. Because the UI of every other browser just feels wrong. Aside from Safari maybe, but Safari's tab bar makes it impossible to handle 50+ tabs.

50+ tabs!!

Re: Camino browser reaches its end

#83

Post by lawl »

redthrowaway wrote: post #38
wtallis wrote: post #36

I 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.

Betterprivacy can kill flash cookies.

NotScripts is still only mitigating JS and not fully blocking it, at least last time I looked at the source (I also almost puked). Plus it lacks feates like clear click (anti clickjacking), ABE etc.

Re: Camino browser reaches its end

#84

Post by gaius »

Samuel_Michon wrote: post #81
gaius wrote: post #78

Earlier quoted context omitted.

From http://caminobrowser.org/blog/2011/#mozembedding As a purely community-based open source project, no one is employed to work on Camino; all Camino developers are volunteers, working on Camino in their spare time, as a labor of love. While maintaining embedding in a fork of Gecko is theoretically possible, we don’t have the manpower for a sustained effort of that kind

Ah, that explains a lot. It also shows the shadow side of open source software development: if the developers get bored, they can just up and leave. If all the devs do so, the project is dead but there’s no one there to call it. Users aren’t owed any explanation.

In this case, the maintainers of a library they depended on were the ones that upped and left.

Re: Camino browser reaches its end

#85

Post by twic »

lttlrck wrote: post #82
masklinn wrote: post #58

Earlier quoted context omitted.

I still love it. To this day it remains my primary browser, through its aged rendering, through its lockups on JS-heavy sites, through its dated icons, through everything. Because the UI of every other browser just feels wrong. Aside from Safari maybe, but Safari's tab bar makes it impossible to handle 50+ tabs.

50+ tabs!!

I know! How does he manage to have so few?

Re: Camino browser reaches its end

#86

Post by freehunter »

TazeTSchnitzel wrote: post #80
vvhn wrote: post #43

Earlier quoted context omitted.

>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) That's because Home and End keys on the Mac, like in the original UNIX, mean the beginning and the end of the document not the beginning and end of a line which is a Windows thin…

>That's because Home and End keys on the Mac, like in the original UNIX, mean the beginning and the end of the document not the beginning and end of a line which is a Windows thing Is it? I'm used to them going to the beginning and the end of lines on Linux.

>and since most early Linux desktop environment's aimed to duplicate Windows, is also the default Linux behaviour now.

Re: Camino browser reaches its end

#87

Post by freehunter »

mhd wrote: post #73

One feature Camino ha and that I really miss in other browsers is that it displayed whether files in its download window were still there. That sounds rather trivial, but made it a perfect "file inbox", where I could quickly see whether I still needed to review/move a file. And the fact that it was more in sync with the OS X desktop experience than Firefox (back in the days; got better) and Safari (brushed metal)...…

Chrome does that download behavior as well. You can see if a file has been removed from the downloads folder right from the downloads tab in Chrome.

Re: Camino browser reaches its end

#88

Post by pilif »

vvhn wrote: post #43
pilif wrote: post #35

Earlier quoted context omitted.

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 G…

>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) That's because Home and End keys on the Mac, like in the original UNIX, mean the beginning and the end of the document not the beginning and end of a line which is a Windows thin…

> You will find this behaviour in all Apple provided applications as well.

not on my machine. As I said, I used ~/Library/KeyBindings/DefaultKeyBinding.dict to change it. If the OS provides a way to change defaults, I expect applications to respect that too - no matter the historical reasons.

> >in the new Gmail compose window, not even Command-Left/Right works

> cntrl-a and cntrl-e work.

Yes, but Command-Left/Right is something that worked on the Mac even since before OSX. I, again, see no reason why it wouldn't work here.

Re: Camino browser reaches its end

#89

Post by pilif »

adventureloop wrote: post #56
pilif wrote: post #35

Earlier quoted context omitted.

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 G…

CMD-Arrow (left,right,up,down) will move you to the beginning of the line, end of line, start of document,end of document respectively. I really miss these keys when I am on windows as I find it much less of a hand movement to do.

Yeah. It just doesn't work in Gmail's new compose window in Firefox. No idea why.
Post reply on HN