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

Firefox Browser Ported to HaikuOS

discuss.haiku-os.org

Post reply on HN
Print view View original

151–160 of 223 posts

Re: Firefox Browser Ported to HaikuOS

#151

Post by asadotzler »

simcop2387 wrote: post #118
guessbest wrote: post #117

Earlier quoted context omitted.

Maybe it hit trademark issues, but the reason I remember from slashdot was that phoenix was already a semi-popular open source project in the debian repository, so firefox had to be named from phoenix to mozilla-phoenix. But firefox at the time still named phoenix just ran so much better on windows than linux, it was funny.

Both Phoenix and Firebird were over the naming and trademark clashes: For firebird, https://www.cnet.com/tech/tech-industry/mozilla-holds-fire-i... and https://www.cnet.com/tech/services-and-software/mozillas-fir... in this case it was AOL Time Warner that owned the Firebird trademark for the database. 2) For Phoenix, https://web.archive.org/web/20070914035447/http://www.ibphoe... the main reporting on it seems to be…

Phoenix was because of a challenge from Phoenix Technologies, the BIOS maker. Firefox was because of concerns about stomping on a small OSS project, the Firebird Database. I was responsible for all of this at Mozilla. Happy to answer any questions.

Re: Firefox Browser Ported to HaikuOS

#152

Post by Lammy »

tialaramex wrote: post #129
pjmlp wrote: post #59

Earlier quoted context omitted.

As someone doing Web development during 1999 - 2002, on a dotcom startup, there were enough people using Mozzilla browsers.

At the turn of the century, Mozilla are trying to ship a web browser (also to be called Mozilla) based on the work they've got from Netscape. They shipped a series of "M" numbered (ie milestone) releases, which preview what we today think about as normal dynamic HTML but at the time it commonly just crashes the entire browser. Like, a colleague was working on code that would reach into the DOM and just tweak the CSS…

> They shipped a series of "M" numbered (ie milestone) releases

Relevant: “A Visual Browser History, from Netscape 4 to Mozilla Firefox” https://www.andrewturnbull.net/mozilla/history.html

Re: Firefox Browser Ported to HaikuOS

#153

Post by dataf3l »

asadotzler wrote: post #150
guessbest wrote: post #117

Earlier quoted context omitted.

Maybe it hit trademark issues, but the reason I remember from slashdot was that phoenix was already a semi-popular open source project in the debian repository, so firefox had to be named from phoenix to mozilla-phoenix. But firefox at the time still named phoenix just ran so much better on windows than linux, it was funny.

No. Phoenix Technologies, the BIOS maker sent me an email telling us they made a BIOS web browser and our name would confuse things. Under advice from our legal support, we agreed to change the name. We changed to Firebird and the OSS database project bombed my inbox (and Mitchell's too) for a week with hundreds of nastygrams and though we were in the clear on TM, we didn't want to stomp on the little OSS project so…

was waterduck considered?

Re: Firefox Browser Ported to HaikuOS

#154

Post by blackenedgem »

dataf3l wrote: post #153
asadotzler wrote: post #150

Earlier quoted context omitted.

No. Phoenix Technologies, the BIOS maker sent me an email telling us they made a BIOS web browser and our name would confuse things. Under advice from our legal support, we agreed to change the name. We changed to Firebird and the OSS database project bombed my inbox (and Mitchell's too) for a week with hundreds of nastygrams and though we were in the clear on TM, we didn't want to stomp on the little OSS project so…

was waterduck considered?

Stormcow

Re: Firefox Browser Ported to HaikuOS

#156

Post by BirAdam »

usrnm wrote: post #58
llm_trw wrote: post #56

Earlier quoted context omitted.

We're getting the United States v. Google case so hopefully history doesn't repeat.

I actually hope that history does repeat itself, and google gets severely punished

Well, it would appear that Google will be forced to stop paying companies to make Google the default search. This is actually kind of a death for Mozilla as that’s where most of their money comes from.

Re: Firefox Browser Ported to HaikuOS

#157

Post by kryptiskt »

prmoustache wrote: post #104
Uvix wrote: post #50

Earlier quoted context omitted.

There were some sites requiring IE6 but not that many, and the improvements like tabs were enough for people switch to Firefox where they could. Unfortunately Mozilla’s refusal to implement process-per-tab, combined with Flash’s instability, let Chrome eat their lunch.

chrome eat their lunch for only one reason: everytime you were doing a google search, google literally begged people to download their browser while half of the smartphone were coming with google chrome by default. In the head of people google and chrome slowly became a synonym of internet the same way the ie icon used to be in the previous decade.

Also, Google paid a ton of money to bundle the Chrome installer with Flash and Adobe Acrobat downloads.

Re: Firefox Browser Ported to HaikuOS

#158

Post by Uvix »

prmoustache wrote: post #104
Uvix wrote: post #50

Earlier quoted context omitted.

There were some sites requiring IE6 but not that many, and the improvements like tabs were enough for people switch to Firefox where they could. Unfortunately Mozilla’s refusal to implement process-per-tab, combined with Flash’s instability, let Chrome eat their lunch.

chrome eat their lunch for only one reason: everytime you were doing a google search, google literally begged people to download their browser while half of the smartphone were coming with google chrome by default. In the head of people google and chrome slowly became a synonym of internet the same way the ie icon used to be in the previous decade.

They're doing that now (and for the last several years). I don't remember them doing that back when Chrome overtook Firefox in 2012, though...

Re: Firefox Browser Ported to HaikuOS

#159

Post by waddlesplash »

rcarmo wrote: post #65
llm_trw wrote: post #34

Earlier quoted context omitted.

The raspberry pie is a very odd computer which is hard to develop for. There are much better targets that are both simpler to develop for, cheaper, and easily available.

And we never really got any of them working, so I would contest that. Many years ago, I asked about Pi 2 support on the Haiku forums and there was a lot of ill will towards Broadcom closed binaries. I pointed at the Plan9 port and a couple more examples and nothing happened. I tried the same thing several times with the Pi 3 and the Pi 4, and someone more vocally pointed towards RISC-V. Some four years later, there i…

The RISC-V port was done almost entirely by one developer who took an interest in it. It wasn't as though the project got together and decided to prioritize RISC-V over ARM; it was just that someone did a port, and then it got (mostly) upstreamed. Nobody has taken an equivalent interest in ARM, in large part because, well, the developers are all running x86 machines as you might expect, so that's what Haiku gets developed on. If someone comes along (or one of the existing developers takes interest) in working on the ARM port more, we will hardly reject the patches!

Re: Firefox Browser Ported to HaikuOS

#160

Post by coolcoder613 »

hodapp wrote: post #130
coolcoder613 wrote: post #39

Earlier quoted context omitted.

Quite a lot of people use Haiku bare metal, and wifi support absolutely is present.

Are you one of them? I am curious what the experience is like trying to use it as anything like a daily system.

I am, although I do not use it as a daily driver, I have bare metal installs on two different computers. In my experience, it is very snappy, and always fast, except for some browsers, and wifi support for my specific wifi cards is there, and works fine, although not perfectly. In regard to using it as a daily system, browser-wise, especially since Firefox has been ported, it works well enough. Webmail can be used fairly easily, but most of the email clients available only support regular pop/imap authentication, and not oauth. But then, whether you can daily drive it depends on your specific use cases and hardware.
Post reply on HN