Eh? Having developed a site that makes not insignificant use of CSS and DOM, I can tell you that at one point in development of the site, if you used Mozilla you could notice the difference, and that wasn't a bad thing. In the end, I used a number of hacks to make sure the site looked correct in IE, but it was a pain. And don't get me started on that awful Opera.
NS6 may have been poor in many areas, but its rendering engine got a lot more right than IE6 does now. NS7/Mozilla1.0RC2 corrects many of NS6's shortcomings and still managed to pull even further ahead of IE in its support for CSS and DOM. After all, why doesn't IE6 support fixed positioning? Konqueror 2.2.2 does for crying out loud.
IE doing something wrong is not an excuse to copy them. I applaud the Mozilla team for not following down the slippery slope.
Huh? Netscape 6.0 had better CSS support than any version of IE has ever had. Seeing as Mozilla's gone from 0.6 to 1.0RC2 in that time, I can only see it been better than any other browser by a long way.
As an example, name a browser that supports getComputedStyle.
I dunno, NS6 should have been 5, even though the stories of "version 5 was canned" which is at least justified (See Mozilla Classic). However, NS7 is a damn site better than NS6 with quite a lot of new features, not to mention it's finally worth recommending to people who aren't geeks.
All in all, version numbers don't matter in the long run, I'm still sceptical about this whole "version numbers mean a lot to dumb users" argument.
One of my web sites uses a Javascript function called isCrappyBrowser(). It does exactly as the name implies, returns true if the user's using a crappy browser:)
Of course, what is crappy browser is up for debate, but it's easy to add or remove browsers from the list.
Actually, the Voodoo2 was a considerable improvement over the Voodoo1. 3dfx then ran into trouble because they were designing Rampage as the successor to the Voodoo2 but it suffered from creeping featurism. When NVIDIA started to overtake them, they started releasing stop-gaps aka the Voodoo3-5.
The sad part is Rampage was nearly ready when 3dfx went under. There are even screenshots of it playing Quake3.
And where is the stated level of support? For example, will it support getComputedStyle? So far, Mozilla is the *only* browser to support that, despite the fact that it's actually quite useful.
Of all the major browsers out there now, Opera has the worst DOM support. This is no secret and promising such a feature is rather useless seeing as you can't just bolt DOM support on, the engine has to be designed around it. Just look at the problems Netscape had.
Actually, unless Opera gains some decent DOM support soon, its time is nearly up. After all, with Netscape 4's market share rapidly becoming insignificant, you'll start seeing a lot more client-side scripting and Opera will get left behind.
Come on, Konqueror's development is happening faster than Opera, it can't be that hard.
I must say I've been quite impressed with Konqueror 3. I recommended people not use Konqueror 2.x because its rendering engine was worse than Opera's, yet version 3 is *very* good.
Opera, on the other hand, is becoming the new Netscape 4. It simply doesn't support modern standards and if you have to support it, you'll be held back if you want to use DOM.
If you want to play CDs, use your CD player. I'd be surprised if a significant number of people didn't have one. And as for DVDs, it would have increased the cost of the GC.
It only really emulates the look, not the feel. There are things such as when you right click on a "scroll down" button, the window actually scrolls up, which is far more elegant than having up and down arrows on the top and bottom of the window IMHO.
IIRC Arthur was only intended as a stop-gap until Acorn could finish their ARX project (Their very own Unix). I believe Arthur got its name because they needed "A Risc os by THURsday", and hence wasn't exactly all that powerful.
Slashdot Mirror
1) 1.0RC2
2) I don't know, but I can't find anything in bugzilla about it.
3) Judging from the article at Mozillazine, could be as early as next week.
Eh? Having developed a site that makes not insignificant use of CSS and DOM, I can tell you that at one point in development of the site, if you used Mozilla you could notice the difference, and that wasn't a bad thing. In the end, I used a number of hacks to make sure the site looked correct in IE, but it was a pain. And don't get me started on that awful Opera.
NS6 may have been poor in many areas, but its rendering engine got a lot more right than IE6 does now. NS7/Mozilla1.0RC2 corrects many of NS6's shortcomings and still managed to pull even further ahead of IE in its support for CSS and DOM. After all, why doesn't IE6 support fixed positioning? Konqueror 2.2.2 does for crying out loud.
IE doing something wrong is not an excuse to copy them. I applaud the Mozilla team for not following down the slippery slope.
Huh? Netscape 6.0 had better CSS support than any version of IE has ever had. Seeing as Mozilla's gone from 0.6 to 1.0RC2 in that time, I can only see it been better than any other browser by a long way.
As an example, name a browser that supports getComputedStyle.
I dunno, NS6 should have been 5, even though the stories of "version 5 was canned" which is at least justified (See Mozilla Classic). However, NS7 is a damn site better than NS6 with quite a lot of new features, not to mention it's finally worth recommending to people who aren't geeks.
All in all, version numbers don't matter in the long run, I'm still sceptical about this whole "version numbers mean a lot to dumb users" argument.
One of my web sites uses a Javascript function called isCrappyBrowser(). It does exactly as the name implies, returns true if the user's using a crappy browser :)
Of course, what is crappy browser is up for debate, but it's easy to add or remove browsers from the list.
Actually, the Voodoo2 was a considerable improvement over the Voodoo1. 3dfx then ran into trouble because they were designing Rampage as the successor to the Voodoo2 but it suffered from creeping featurism. When NVIDIA started to overtake them, they started releasing stop-gaps aka the Voodoo3-5.
The sad part is Rampage was nearly ready when 3dfx went under. There are even screenshots of it playing Quake3.
And where is the stated level of support? For example, will it support getComputedStyle? So far, Mozilla is the *only* browser to support that, despite the fact that it's actually quite useful.
Err...not only did you forget the Voodoo2 and get the name of the Voodoo3 wrong, you don't even know the feature sets of the appropriate cards.
The Voodoo3 was pretty much a Banshee with an extra TMU and a faster clock. The T-buffer didn't arrive until the Voodoo5.
Is there any actual evidence of this? You can't just magic up a new rendering engine on a whim.
Of all the major browsers out there now, Opera has the worst DOM support. This is no secret and promising such a feature is rather useless seeing as you can't just bolt DOM support on, the engine has to be designed around it. Just look at the problems Netscape had.
Here's one:s htmlh edule_ moz.php3?force_tree=1
http://truffula.net/~quotemaster/countdown.
http://homepages.nildram.co.uk/~dwinsper/sc
That second one also shows Opera's lack of support for fixed positioning. While they may not validate, it is not the reason they don't work in Opera.
Actually, unless Opera gains some decent DOM support soon, its time is nearly up. After all, with Netscape 4's market share rapidly becoming insignificant, you'll start seeing a lot more client-side scripting and Opera will get left behind.
Come on, Konqueror's development is happening faster than Opera, it can't be that hard.
I must say I've been quite impressed with Konqueror 3. I recommended people not use Konqueror 2.x because its rendering engine was worse than Opera's, yet version 3 is *very* good.
Opera, on the other hand, is becoming the new Netscape 4. It simply doesn't support modern standards and if you have to support it, you'll be held back if you want to use DOM.
Actually, most of the problems are caused by Opera supporting sod-all of DOM.
They were forced to back off because of threats of antitrust action.
If you want to play CDs, use your CD player. I'd be surprised if a significant number of people didn't have one. And as for DVDs, it would have increased the cost of the GC.
It only really emulates the look, not the feel. There are things such as when you right click on a "scroll down" button, the window actually scrolls up, which is far more elegant than having up and down arrows on the top and bottom of the window IMHO.
IIRC Arthur was only intended as a stop-gap until Acorn could finish their ARX project (Their very own Unix). I believe Arthur got its name because they needed "A Risc os by THURsday", and hence wasn't exactly all that powerful.
RISC OS 2 could run in 512K with a fair bit to spare, but it would be a push to fit it in 288K.
It's also got one of the worst rendering engines I have ever seen.
Konqueror has its fair share of limitations though, such as bugs in fixed positioning and a slightly weaker DOM than Mozilla.
You show me a CSS and DOM2 compliant browser that works quickly on a P166 and you might have a point.
It's just a statement with no supporting evidence.
Red Hat change the major version number when they break binary compatibility. Since 7.3 is binary compatible with 7.0, they didn't go to 8.0
No it's not, it presents no supporting evidence whatsoever, so it's nothing more than an AC making a claim.