Firefox 1.0 – Now where’s the BeOS release?!

Yeah, I know… I’m a jerk sometimes — and I think many of us take the bezilla folks for granted. Shame really, they’ve put in a ton of hard work, and since I don’t think they hear it enough…

THANKS

Now consider this me pleading for a stable Firefox 1.0 for R5 (net_server).

In other news it seems YellowTab made a release and forgot to include gzip or gunzip. Exactly how such a glaring and stupid mistake gets past QA of a company is beyond me. Let alone a company which asks their customers to believe they’re a highly professional outfit capable of creating and sustaining a market that doesn’t even bloody exist.

Of course, since the people having the problems are essentially paying to alpha-test software (and have been paying repeatedly for that priviledge for several years) who can complain? Chalk up another under “grave incompetance” for YT.

Oh, and just to clarify, I’m not knocking the YT devs – I’m knocking their business and management. It’s pathetic.

3 Responses to “Firefox 1.0 – Now where’s the BeOS release?!”

  1. Mikael Jansson Says:

    I agree. yellowTAB _seriously_ need proper QA & Testing.

    Also, they shouldn’t just throw in any app even if it’s not finished; just look at the playlist window in “Champion”. Parent directory and “Reload directory” (???) in the same view as the other folders, with the _exact same_ icons!

  2. MYOB Says:

    Forgot to include gzip?

    HAHAHAHAHAHAHAHAHA! (repeat ad nausiem for ten minutes, tears rolling down cheeks)

    They’ve pissed me off so much recently that they now have explicit instructions that if they use my Intel i8xx graphics driver before I’ve opened the source, I’m suing them. They’re so incompetent, so hypocritical, etc. Steal from the community, make said community pay HUGELY to use it…

    Oh, and their English translator obviously sucks.

  3. Simon Says:

    Firefox 1.0 release:

    Hey Bryan, check out the bezilla blog: http://www.livejournal.com/community/bezilla/

    There are some new BeOS-specific bugs that seriously affect firefox’s usability at the moment. We’re working through the list, and have just scheduled a release date of December 5th.

    And both myself and neils use net_server, so they’ll definately be a build for you.