Netscape 8 Breaks IE XML
An anonymous reader writes "Microsoft has alerted users that Netscape's latest browser appears to break the XML rendering capabilities in Microsoft Internet Explorer. Dave Massy, a senior programme manager for IE, warned users in a blog posting that after installing Netscape 8, IE will render XML files as a blank page, including XML files that have an XSLT transformation. What a week for Netscape 8.0; first the browser needed several fixes hours after its release, then it was discovered that without IE installed, Netscape 8.0 will not install, and now IE needs Netscape uninstalled to work."
I haven't tried out Netscape 8.0 (Firefox is fine with me for now), but what are some reasons people are switching to Netscape 8.0?
Does anyone have any stats on how many people are even using it? What are the website statistics showing?
To me this sounds like Netscape ran into a "too little, too late" situation with their newest iteration of their browser.
Back in the day, I was a big Netscape fan, and I waas really hoping that this new release would bring them back as a player, but enough is enough, guys. Three strikes, and you are OUT.
One more thing...
<zealot>
Firefox rules...IE sucks...let's fight!
</zealot>
^_^
____
~ |rip/\/\aster /\/\onkey
*IE needs Netscape uninstalled to work.* /me runs out to install Netscape 8.
Pulp Audio Weekly - Geek News and Reviews
Having a hard time. Who is evil here?
If I recall correctly, your submission came up as a blank screen...
This comment does not necessarily represent the views and opinions of the author.
I stopped using Netscape after AOL bought it! Kept using NS4.7 (and later IE), until Firefox appeared.
Repeat after me: Netscape, Is, Now, Just, A, Brand.
I think I'll just quietly install NS8 on all of my clients' boxes before they fix this 'feature'.
No need to tell them about it, though... Just leave them using Firefox.
Sometimes boldness is in fashion. Sometimes only the brave will be bold.
It's amazing how quickly everyone forgets the IE 4 chaos....
instance where an arbitrary and totally meaningless deadline for launch wrecked havoc on software.
Releasing Netscape based on Firefox 1.03 after 1.04 was available with important security fixes was completely idiotic if a key differentiator of Netscape is supposed to be superior security!
And then releasing an updated version within 24 hours based on 1.04 to show the world they could simply have delayed the initial launch by a day in the first place proved their mismanagement (any excuse about changing to 1.04 being complex and delaying the launch too much went out the window).
Now their bragging rights about being able to switch betweeen IE and Firefox rendering is damaged because they didn't test enough to find out if their product breaks existing functionality like displaying XML?
Not Netscape-specific but for software in general...Managers, get a clue, if you don't like deadlines given by engineers then remove features until they can provide timeframes that are acceptable. And you engineers that are too cowardly to say "No, that cannot be done by that time unless we eliminate/postpone some of the requirements" get some balls.
!seineew era sreenigne epacsteN :)
the New netscape is owned by AOL, and really has nothign to do with Mozilla... that connection has long ago been severed.
I lot of folk in this thread seem not to realize that.
If it already is broken, do you *really* break it?
Apple built a platform for their ideas, Google built one for everyone's.
You *could* screw up a *nix system with a bad installer, but it is harder to do for a couple of reasons:
1 -- you usually only need to run the installer as root if you are doing a system-wide installation. If it is just for you it is easier just to install it in your home folder. Personally, I do that fairly often. I have an updated version of whatever I was installing in my space and can fall back on the system-wide version if I foobar it somehow.
2 -- *nix apps are generally more self-contained than Windows apps. The fact that much of the configuration information for Windows programs resides in the registry is just asking for problems. For example:
If program A uses protocol X and program B does so also, installing B may change registry entries concerning protocol X so that they match its needs. Program A stops working with protocol X.
The *nix tradition of self-contained configuration files avoids the collisions that can arise in the registry.
So again, YES, it is possible for an installer to completely wreck a *nix box BUT it is much less likely.
Life is short: void the warranty.
Really, just looking at the Microsoft Fanboys referenced in that article.
"Internet Explorer (7?) is all I need."
"Honestly, the rubbish you [Microsoft] have to put up with... my heart goes out to you guys. Keep up the good work with IE7"
Yes, people, we are eulogising about software that hasn't even been released yet.
I thought the point with Netscape is that it is meant to be an IE-replacement - hence the render using IE engine feature. Whether it respects an obsolete, badly coded application it is designed to get rid of is kinda irrelevant.
Obviously, this is a bug that needs to be fixed, but let's not start burying Netscape yet. More competition is always good.
IE already renders a great number of XML pages as blank, without the help of Netscape.
Gentoo installs first in an isolated sandbox (a fake root) which prevents a malicious installation program destroying the system. When the installation program is complete, portage finds the files which were installed into the sandbox and copies them across to the real system, keeping a note of which files belong to the packages, so that they can easily be removed later.
So although the problem of installing packages without wrecking your system has been solved already.
Out of interest, how do other distros approach it?
I'll probably be modded down for this...
Kinda reminds me of back in the day, when I was a lowly tech-support person at a small, "national" ISP (we used UUnet's POPs)...
We used to routinely--and by routinely, I mean that they constituted at least 75% of our calls--get a lot of people calling in with the same problem: they could dial into AOL just fine, but their computer couldn't successfully negotiate a connection with our (UUnet's) modems. It would just break down during the handshaking process and give one of several predictable errors.
Well, it turns out that whatever AOL was using in their specialized dial-up adapter broke the standard windows dial-up adapter. As soon as you nuked and reloaded the standard MS-provided Dial-Up Adapter from the Windows CD (a process I could still do in my sleep to this day, I've done it so many hundreds of times), those people could connect to our (UUnet's) POPs just fine. But guess what: if those people EVER dialed back into AOL--even if they just attempted to dial and then aborted the process--it would immediately re-break the standard MS-provided dial-up adapter and they'd soon be back on the phone with our tech support people.
Now fast forward to today, and who owns Netscape? Oh, that's right... it's AOL, so I guess this is just a more modern interpretation of their same old slimy tactics. What scumbags and/or incompetents they are.