Slashdot Mirror
Mozilla 1.4b Loosed
An anonymous reader writes "The fine Mozilla folks have decided to bless us with the release of Mozilla 1.4b this weekend. Highlights include support for NTLM authentication, usability improvements, and lots of performance, stability, and site compatibility fixes. As always, the release notes have more detailed info on changes."
Much more closely than I do now. After 1.0 the improvements seemed less noticeable to me. I suppose this means the software has matured. Is anyone really excited about the new features? Are they interesting from an end user perspective?
Actually, that could be a good thing. It may lead to a deployment of Mozilla within an organization that has resources secured by MS server packages (IIS, SQL Server, etc).
In my opinion this shows the Mozilla team being a bit more agressive in making inroads into the corporate (sometimes MS-dominated) world. Good for them.
Wearing pants should always be optional.
Many people will consider NTLM support as superfluous pro-MS bloatware and another useless addition to Mozilla.
:)
I'd like to point out this is just plain wrong. There are many developers that are forced to use IE to do their job just because the company's product runs on IIS and uses NTLM.
Mozilla supporting NTLM means better ways of testing software for these developers, as well as giving a better idea of the web homogeneity of the product.
Free myself from IE at work ! Go for NTLM, Mozilla !
Karma cannot be described by words alone.
Because, if one component crashes, the other does also. They are that integrated.
Mozilla is considered to be the flagship open source browser, and one of the strengths of the open source desktop lineup. Therefore, a lot of open source fanboys are interested in its progress. Opera is of interest to a far smaller subset of people, seeing as it has neither the standards compliance, platform support, or freedom (beer and speech) of Mozilla. I'm not saying Opera doesn't have it's strengths, but a lot of people are more interested in Mozilla than Opera.
It's hard to be religious when certain people are never incinerated by bolts of lightning.
IMHO if the mozilla developers organized one thread or one fork per window - they would be better off. If they are interested in doing this - then they should change the way malloc() is handled.
What do you mean by "better off"? Would it fix bugs? Improve latency? Or what?
Ever heard of profiling? If you think that something's slow, or inefficient, you profile it to figure out where the inefficiencies are. Believe me, if malloc showed up on the list, it would have been optimized long ago (and from what I understand, Mozilla already does some pretty clever things with malloc).
You're trying to suggest a solution, when you haven't even established a problem. Until you have some gprof or cachegrind output proving that more malloc kung fu is needed, I doubt any Mozilla developers will listen to you.
Besides, your original premise is that Mozilla needs one thread per window. What about the networking thread? Do you know anything about how a modern web browser is implemented or are you just making up random junk?