141–150 of 223 posts
I have said it before, Haiku feels like it is simultaneously 20 years in the future and 20 years in the past. The interface is so incredibly snappy but there is a lot of basics missing such as WiFi support. Seeing a modern browser supported does fill a big gap however. Who knows maybe one day through a series of silly unpredictable events it will be the OS of choice and running Ladybird browser in a similar fashion.
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
Earlier quoted context omitted.
WiFi support missing? Afaik it uses *BSD network "drivers" and I remember having a wifi dialog/support Edit: https://www.haiku-os.org/docs/userguide/en/workshop-wlan.htm... here wifi seems to be working (which another commenter pointed out as well)
It doesn't support a lot of modern Wi-Fi chipsets. There was an entire wave of Broadcom-powered stuff that they weren't able to develop for.
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
Google was force feeding Chrome to everyone at google.com.
Earlier quoted context omitted.
As someone doing Web development during 1999 - 2002, on a dotcom startup, there were enough people using Mozzilla browsers.
Yeah. We were all sick of loading a website with Internet Explorer and getting 1930201 hot toolbars, blinking 'desktop buddies' and 32 new system tray icons with programs running. Phoenix saved us.
Earlier quoted context omitted.
Palm bought BeOS back in the day, but they didn't do anything with it. It was spun out with the PalmOS into Palmsource when Palm went to other OSes, so it didn't follow the rest of Palm into HP (and then LG). Palmsource was then swallowed by a Japanese company called Access, which was and apparently still is making a browser for embedded applications called Netfront.
Palmsource did open-source Binder, which is still around, and widely used.
Earlier quoted context omitted.
Exactly what I thought as well. UIs get increasingly slower as time passes, not snappier. We had snappy UIs in the 80s and 90s.
I don't remember Windows 95 & MS Word 6 being especially snappy. I think this is nostalgia.
Some history about Firefox and BeOS. Before Firefox, there was Mozilla, which had a BeOS port (called Bezilla). Bezilla was bloated and slow. So the BeOS community tried to make a stripped version of Mozilla with only the browser (minus all the bloat). This project became an inspiration to do the same for Mozilla, and that product became Firebug (or something similar - edit phoenix, then firebird), which due to trade…
Native front ends like Galeon on Linux and Chimera/Camino on Mac inspired Firefox (m/b->Phoenix->Firebird->Firefox, my bad that naming mess was also my fault, see Chimera->Camino for more of my handy work with AOL lawyers right before Netscape shuttered and we got our independence with MoFo.)
We kept XUL because Dave made it great on Windows so no native front end but that let us preserve extensions and re-used a few key widgets in XPToolkit easily.
Bezilla was just another Mozilla suite port, one of about a dozen at the time, one that never got any core Mozilla team attention except as a niche port we were happy to host, so suggesting it was inspiration for what Blake and I did to get Firefox going (and later Ben, Dave and Joe and others) is a bit off-track.
Earlier quoted context omitted.
It wasn't Firebug, that was a developer tool extension. It was first Phoenix which hit trademark issues, and then Firebird which hit trademark issues, which then became Firefox.
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.
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 we changed again.
I was at the whiteboard when Jason Kersey of mozBin, mozillaZine, and later Chrome fame came up with Firefox. We had two columns of names, forces of nature and animals and were pairing them up.