You are viewing bezilla

BeZilla blog - Time for something completly different?
December 17th, 2008
09:18 am
[tqh]

[Link]

Previous Entry Share Next Entry
Time for something completly different?
I've grown (very) tired of trying to get code into Mozilla base. I just failed getting a patch reviewed that increases stability, quality and speed of Mozilla on the sole argument that they don't like a structure in the OLD Mozilla-code (and I don't change it structurally). This means it won't go into Firefox 2 and there is no chance to fix that now. Adding stuff to a 310k patch isn't very smart anyway, especially when it's something that would be much more suited for a bug of it's own.

Anyway...

Now that Firefox 2 is nearing end of life*, it's a good time to stop for me as well.

I'll be around, but I won't be working much on anything I need to talk with Mozilla about.

*) And without any BeOS/Haiku improvements at all since I've been stuck waiting for this review.

(8 comments | Leave a comment)

Comments
 
[User Picture]
From:fyysik
Date:December 17th, 2008 10:40 am (UTC)
(Link)
Well, when I told about newer gcc problems, I rather meant similar problems - it will be very hard to convince people to allow "legacy/compatibility" code changes - than technical side of problem.
From:tigerdog
Date:December 17th, 2008 04:45 pm (UTC)
(Link)
I understand your frustration. The mozilla folks don't seem to appreciate the efforts we've made to stay current with (really) only two contributing developers over the last 5 years... I don't count myself.

Anyway, maybe you can throw yourself into the webkit port and help develop a new browser for Haiku?

In the meantime, I'm going to place a comment in the bug expressing my displeasure.
From:kokitomare
Date:December 17th, 2008 05:23 pm (UTC)

For it

(Link)
Just fork the branch, host it elsewhere (BePorts?), give it a different name and kiss the mozilla bureaucracy goodbye, at least for now. It will make your life easier and more productive. :)

Or, as Tigerdog suggested, move to webkit. Although I don't know if you will not run into the same kind of problems...
From:tqh
Date:December 17th, 2008 06:52 pm (UTC)

Re: For it

(Link)
Forking would be a good idea if I had any interest in continuing to work on it. I don't.
From:tigerdog
Date:December 17th, 2008 09:27 pm (UTC)

so why does it work...

(Link)
...with the BeOS-specific structures removed from prio.h? Just for fun, I commented out the beos-specific lines and built tqh's new NSPR with the standard ones. I can't see any difference.

Does anyone know why BeOS has non-standard structures in the first place? Maybe something to do with R5 Netserver?
From:tqh
Date:December 17th, 2008 10:12 pm (UTC)

Re: so why does it work...

(Link)
Yes, it works but probably with side-effects. My guess is this is where the ssh problem might be.
From:tigerdog
Date:December 19th, 2008 12:14 am (UTC)

Re: so why does it work...

(Link)
It appears the smaller structure was made to accomodate Netserver. If I read the BeBook correctly

struct sockaddr_in {
unsigned short sin_family;
unsigned short sin_port;
struct in_addr sin_addr;
char sin_zero[4];
};

the difference is in the length of pad at the end. Be libnet.so uses a shorter structure with 4 bytes of pad, compared to 8 bytes of pad at the end that Mozilla seems to expect in the usual bind implementation. Could that really be the only difference? If it is, it still shouldn't make any difference in real life if we use the standard header; won't we just lose the last 4 bytes of pad? Or will it blow up when we try to run under Netserver?
From:emitrax
Date:January 1st, 2009 04:19 pm (UTC)

Move to webkit

(Link)
You should definitely move to webkit and start working on a native browser for Haiku. Have you think of that? Keep up the good work guys!
Mozilla for BeOS project Powered by LiveJournal.com