this turned out to be a bug in XFree86's Xlib implementation of all places. The next 3.x version as well as XFree86 4.0 will fix this problem. Thanks goes to Keith Packard of the XF86 team for helping Netscape track this down!
Actually, that is 100% javascript. If you don't recognize it you should go read up on JS. Remember, JavaScript is a language, and like many other languages, you import libraries which add new library calls, but the language is still fundamentally unchanged.
The documentation should be fixed if it says what you claim...sure enough, I found the document you're referring to, and it's just outdated. I'll try to fix it this weekend.
Components written in JavaScript are true XPCOM components. It was actually shaver (who you replied to) who wrote the support for JavaScript components... I think he knows what he's talking about
Don't blame Mozilla for Linux's shortcomings.
on
Mozilla M10 Released
·
· Score: 1
This post is a crock. Netlib was rewritten because the original was a poorly designed, shaky single-threaded hack and had outlived it's usefulness. It was costing MORE developer hours to work around the old netlib than it would have to rewrite the darn thing.. so it was rewritten.
By rewriting it to be a multi-threaded library, we discovered shortcomings in glibc 2.0. After talking with the glibc developers, they themselves said that making it work would 2.0 would be way too much trouble to try to support 2.0. On the other hand, they have made glibc 2.1.2 more robust thanks to holes that Mozilla exposed.
Mozilla is perhaps the most complex desktop application ever to run on Linux. It exercises almost every aspect of Linux and reveals its strengths AND shortcomings. Don't blame the mozilla team because linux and related projects aren't absolutely perfect...if anything the mozilla project has driven linux-oriented projects like glibc to be better - to meet and exceed existing non-free solutions.
Mozilla has nothing to do with Communicator 4.x
on
Netscape 4.6
·
· Score: 2
First of all, Netscape has contractual (customer) obligations to continue to fix bugs in the 4.x series, so Netscape will continue to put out new 4.x releases on a regular basis with more and more bugfixes. Secondly, the team that works on 4.x is a TOTALLY different team than the Mozilla/5.0 team. The Mozilla team is NOT distracted by 4.x work.
Use the glibc2 version if you can!
on
Netscape 4.6
·
· Score: 2
If you have a Redhat 5.x system, or another Linux distribution that has glibc, use that version!
the glibc2 version will be much more stable on these systems than the libc5 version.
I'm not sure why it's still in the unsupported section - it works better than the libc5 version.
Re:Redhat 6.0 and Netscape (Specifically glibc2.1)
on
Netscape 4.6
·
· Score: 3
No - not in 4.6, MAYBE 4.7. And yes, that's an official response:) - I worked on 4.5 and currently work on 5.0
Slashdot Mirror
this turned out to be a bug in XFree86's Xlib implementation of all places. The next 3.x version as well as XFree86 4.0 will fix this problem. Thanks goes to Keith Packard of the XF86 team for helping Netscape track this down!
The documentation should be fixed if it says what you claim...sure enough, I found the document you're referring to, and it's just outdated. I'll try to fix it this weekend.
Components written in JavaScript are true XPCOM components. It was actually shaver (who you replied to) who wrote the support for JavaScript components... I think he knows what he's talking about
Go read http://www.mozilla.org/scriptable/
By rewriting it to be a multi-threaded library, we discovered shortcomings in glibc 2.0. After talking with the glibc developers, they themselves said that making it work would 2.0 would be way too much trouble to try to support 2.0. On the other hand, they have made glibc 2.1.2 more robust thanks to holes that Mozilla exposed.
Mozilla is perhaps the most complex desktop application ever to run on Linux. It exercises almost every aspect of Linux and reveals its strengths AND shortcomings. Don't blame the mozilla team because linux and related projects aren't absolutely perfect...if anything the mozilla project has driven linux-oriented projects like glibc to be better - to meet and exceed existing non-free solutions.
BTW: The bug is #8849
First of all, Netscape has contractual (customer) obligations to continue to fix bugs in the 4.x series, so Netscape will continue to put out new 4.x releases on a regular basis with more and more bugfixes. Secondly, the team that works on 4.x is a TOTALLY different team than the Mozilla/5.0 team. The Mozilla team is NOT distracted by 4.x work.
If you have a Redhat 5.x system, or another Linux distribution that has glibc, use that version!
the glibc2 version will be much more stable on these systems than the libc5 version.
I'm not sure why it's still in the unsupported section - it works better than the libc5 version.
No - not in 4.6, MAYBE 4.7. And yes, that's an official response :) - I worked on 4.5 and currently work on 5.0