Firefox Browser Ported to HaikuOS • Hacker News Board

Re: Firefox Browser Ported to HaikuOS

#221

Post by guessbest » Tue, Aug 13, 2024, 2:52 PM UTC

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…

It was Firebird. Thanks for correcting me.

Re: Firefox Browser Ported to HaikuOS

#222

Post by Vinnl » Wed, Aug 14, 2024, 3:44 PM UTC

MattTheRealOne wrote: post #116

Vinnl wrote: post #103

Earlier quoted context omitted.

I wonder how true that is in absolute numbers, given how many more people are online (/exist) now.

According to Mozilla's own numbers, Firefox Monthly Active Users have been trending down for years and are currently sitting at around 155 million. Source: https://data.firefox.com/dashboard/user-activity

Ah right, forgot that I can just check that in the open reports :)

Re: Firefox Browser Ported to HaikuOS

#223

Post by titusjohnson » Thu, Aug 15, 2024, 4:24 PM UTC

cmrdporcupine wrote: post #63

cdman wrote: post #44

Earlier quoted context omitted.

I guess Firebug was the original "developer tools": https://getfirebug.com/

It was an amazing revolution that made complex app development of JS based front ends finally tolerable.

It flat-out made training people on CSS tolerable. I could have them install the Bookmarklet (before it became an Extension), show them how to use it, and boom, instant productivity boost. Being able to dig through the DOM and figure out what element was applying excessive margin or padding reduced 80% of my "heeeelp!" requests.

Within months I couldn't imagine working without it.