With that logic, you as head of Adobe would continue to test Photoshop 4 against current windows updates then wouldn't you. At some point you just expect HTML to render don't you?
For web application developers this attitude is unreasonable. You can't possibly test your development code and every previous release against every browser variant every night. The other point you seemed to miss is that Mozilla's bug BROKE CODE THAT WORKED WHEN IT WAS RELEASED.
The point of this whole discussion isn't that there was some new release, but that Mozilla was actually nimble enough to respond as quickly as they did.
You keep trying to turn this into some ugly flame war over who has better development practices. Take a valium.
If you took the time to see I didn't post the original one liner that/. published you'd realize I wasn't the author.
Second, if you did work for me you'd be making deep into the 6 figure range like most Oracle savvy developers and you would hardly fall into the underpaid and overworked category.
Third, the reason f&%ktards like you don't work for me is exactly the attitude you exhibited in your last post.
I was working on Sperry systems making more money that your dad ever took home when you were still puking formula onto your mommy's blouse. Check the attitude at the door unless you want to walk out with a flat dic%.
I posted this on an earlier post but I thought it more relevant to re-post here as it's fits in nicely with the above comment.
We were actually one of the companies that found the bug shortly after the release of 2.0.0.10 and if you can't see why this is news then I'm really glad you don't work on my dev team.
Just so we're clear on what the bug ACTUALLY was, the bug specifically effected the canvas drawing capability in the browser. It's not something they test for and frankly, given our experience developing for IE, it's not one they test for either (if IE's random and aberrant behavior is any indication, hell MS can't even make a browser that displays content in a compliant manner given the HTML spec).
A number of sites and web applications use this functionality specifically for navigation, and when Firefox was updated to 2.0.0.10 on many client machines automatically, some business critical web applications were seriously effected. Because of this it was a pretty serious issue.
The reason this IS news is because after confirming the bug and determining the extent of the effect on the user base, the Mozilla folks had nightly builds in our hands just hours after a fix was checked in. This got most of the immediately effected back to work within hours.
A number of us then independently verified the fix against our code and then provided rapid feedback to the team so they could issue a release.
This resulted in an astonishingly fast turnaround. I think the Mozilla folks are to be commended for both not resisting requests for a new release, and the speed with which they were able to respond to a bug effecting business critical web applications. If this had been MS we would have spent 2 weeks navigating mindless support bureaucracy and then fought with management excuses as to why a fix just "can't be turned around overnight." We would have then been forced to contact all of our customers and go into long, boring explanations most of them would never have understood... it's all down hill from there.
Why this IS big news: It is a really bright and shining example of why this type of development is succeeding even in a situation where recursion testing fails (and if you think recursion testing can't fail then you just haven't been developing long enough).
The other good thing that came out of this is we now have a mechanism where developers can subscribe to a mailing list alerting then to pending releases.
Not only did Mozilla respond with a technical fix to the bug AND promptly issue a release which addressed the issue, but they were humble enough to recognize there was a process related problem that needed addressing as well; they fixed that too.
Sometimes I just shake my head in bewilderment at the general idiocy of some posts by/. users.
We were actually one of the companies that found the bug shortly after the release of 2.0.0.10 and if you can't see why this is news then I'm really glad you don't work on my dev team.
Just so we're clear on what the bug ACTUALLY was, the bug specifically effected the canvas drawing capability in the browser. It's not something they test for and frankly, given our experience developing for IE, it's not one they test for either (if IE's random and aberrant behavior is any indication, hell MS can't even make a browser that displays content in a compliant manner given the HTML spec).
A number of sites and web applications use this functionality specifically for navigation, and when Firefox was updated to 2.0.0.10 on many client machines automatically, some business critical web applications were seriously effected. Because of this it was a pretty serious issue.
The reason this IS news is because after confirming the bug and determining the extent of the effect on the user base, the Mozilla folks had nightly builds in our hands just hours after a fix was checked in. This got most of the immediately effected back to work within hours.
A number of us then independently verified the fix against our code and then provided rapid feedback to the team so they could issue a release.
This resulted in an astonishingly fast turnaround. I think the Mozilla folks are to be commended for both not resisting requests for a new release, and the speed with which they were able to respond to a bug effecting business critical web applications. If this had been MS we would have spent 2 weeks navigating mindless support bureaucracy and then fought with management excuses as to why a fix just "can't be turned around overnight." We would have then been forced to contact all of our customers and go into long, boring explanations most of them would never have understood... it's all down hill from there.
Why this IS big news: It is a really bright and shining example of why this type of development is succeeding even in a situation where recursion testing fails (and if you think recursion testing can't fail then you just haven't been developing long enough).
The other good thing that came out of this is we now have a mechanism where developers can subscribe to a mailing list alerting then to pending releases.
Not only did Mozilla respond with a technical fix to the bug AND promptly issue a release which addressed the issue, but they were humble enough to recognize there was a process related problem that needed addressing as well; they fixed that too.
Hell, I'd kick in $100 or $200, maybe more. If this was done as a pure open source project and it was community funded I can see this getting $10 million in public funding in a hearbeat. In fact, from the slashdot community alone we could probably come up with the $2 million they need to hit the next milestone.
If this yields results imagine the direct impact it would have o every one of us. How much would be raised if just 1 in 100 of us donated the equivelant of one month's electricity bill. Mine's over $100 a month...
Anyone got a spare web server that can be set up as a simple e-commerce site? Anyone familiar enough with setting up a 501c3 to fund his research?
Slashdot Mirror
For web application developers this attitude is unreasonable. You can't possibly test your development code and every previous release against every browser variant every night. The other point you seemed to miss is that Mozilla's bug BROKE CODE THAT WORKED WHEN IT WAS RELEASED.
The point of this whole discussion isn't that there was some new release, but that Mozilla was actually nimble enough to respond as quickly as they did.
You keep trying to turn this into some ugly flame war over who has better development practices. Take a valium.
Second, if you did work for me you'd be making deep into the 6 figure range like most Oracle savvy developers and you would hardly fall into the underpaid and overworked category.
Third, the reason f&%ktards like you don't work for me is exactly the attitude you exhibited in your last post.
I was working on Sperry systems making more money that your dad ever took home when you were still puking formula onto your mommy's blouse. Check the attitude at the door unless you want to walk out with a flat dic%.
E
We were actually one of the companies that found the bug shortly after the release of 2.0.0.10 and if you can't see why this is news then I'm really glad you don't work on my dev team.
Just so we're clear on what the bug ACTUALLY was, the bug specifically effected the canvas drawing capability in the browser. It's not something they test for and frankly, given our experience developing for IE, it's not one they test for either (if IE's random and aberrant behavior is any indication, hell MS can't even make a browser that displays content in a compliant manner given the HTML spec).
A number of sites and web applications use this functionality specifically for navigation, and when Firefox was updated to 2.0.0.10 on many client machines automatically, some business critical web applications were seriously effected. Because of this it was a pretty serious issue.
The reason this IS news is because after confirming the bug and determining the extent of the effect on the user base, the Mozilla folks had nightly builds in our hands just hours after a fix was checked in. This got most of the immediately effected back to work within hours.
A number of us then independently verified the fix against our code and then provided rapid feedback to the team so they could issue a release.
This resulted in an astonishingly fast turnaround. I think the Mozilla folks are to be commended for both not resisting requests for a new release, and the speed with which they were able to respond to a bug effecting business critical web applications. If this had been MS we would have spent 2 weeks navigating mindless support bureaucracy and then fought with management excuses as to why a fix just "can't be turned around overnight." We would have then been forced to contact all of our customers and go into long, boring explanations most of them would never have understood... it's all down hill from there.
Why this IS big news: It is a really bright and shining example of why this type of development is succeeding even in a situation where recursion testing fails (and if you think recursion testing can't fail then you just haven't been developing long enough).
The other good thing that came out of this is we now have a mechanism where developers can subscribe to a mailing list alerting then to pending releases.
Not only did Mozilla respond with a technical fix to the bug AND promptly issue a release which addressed the issue, but they were humble enough to recognize there was a process related problem that needed addressing as well; they fixed that too.
ER
We were actually one of the companies that found the bug shortly after the release of 2.0.0.10 and if you can't see why this is news then I'm really glad you don't work on my dev team.
Just so we're clear on what the bug ACTUALLY was, the bug specifically effected the canvas drawing capability in the browser. It's not something they test for and frankly, given our experience developing for IE, it's not one they test for either (if IE's random and aberrant behavior is any indication, hell MS can't even make a browser that displays content in a compliant manner given the HTML spec).
A number of sites and web applications use this functionality specifically for navigation, and when Firefox was updated to 2.0.0.10 on many client machines automatically, some business critical web applications were seriously effected. Because of this it was a pretty serious issue.
The reason this IS news is because after confirming the bug and determining the extent of the effect on the user base, the Mozilla folks had nightly builds in our hands just hours after a fix was checked in. This got most of the immediately effected back to work within hours.
A number of us then independently verified the fix against our code and then provided rapid feedback to the team so they could issue a release.
This resulted in an astonishingly fast turnaround. I think the Mozilla folks are to be commended for both not resisting requests for a new release, and the speed with which they were able to respond to a bug effecting business critical web applications. If this had been MS we would have spent 2 weeks navigating mindless support bureaucracy and then fought with management excuses as to why a fix just "can't be turned around overnight." We would have then been forced to contact all of our customers and go into long, boring explanations most of them would never have understood... it's all down hill from there.
Why this IS big news: It is a really bright and shining example of why this type of development is succeeding even in a situation where recursion testing fails (and if you think recursion testing can't fail then you just haven't been developing long enough).
The other good thing that came out of this is we now have a mechanism where developers can subscribe to a mailing list alerting then to pending releases.
Not only did Mozilla respond with a technical fix to the bug AND promptly issue a release which addressed the issue, but they were humble enough to recognize there was a process related problem that needed addressing as well; they fixed that too.
ER
Oddly missing were a host of good Linux offerings like Kopete (the built in kde client).
Oh.. they will... but the performance is so horrible it is almost unusable. Try hooking it up to a big NFS based NAS or SAN and moving some real data.
If this yields results imagine the direct impact it would have o every one of us. How much would be raised if just 1 in 100 of us donated the equivelant of one month's electricity bill. Mine's over $100 a month...
Anyone got a spare web server that can be set up as a simple e-commerce site? Anyone familiar enough with setting up a 501c3 to fund his research?
This just seems like a no brainer to me.
ElR
I'll eat three cans of the damn things just for the entertainment value of sending them in... I won't have had this much fun in months! El R
That's absurd. I'd buy it the other way around. If anything it should work better on Linux.