Linked by Thom Holwerda on Fri 14th May 2010 18:35 UTC
Thread beginning with comment 424802
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
More Features »
Sponsored Links



Member since:
2005-07-06
Not very.
Adobe cannot get themselves out of the hole they are in until they first admit that they are wrong.
Watching this train wreak unfold is both sad and fascinating.
It reminds me very much of the claim that Adobe made that they never ship final versions of Flash with known crashes. We all know about the the bug that caused Flash to crash, had been existence for 16months and not a single thing was done by Adobe to provide an update to fix that bug until some heat was put underneath them.
From what I understand 'Pepper NPAPI' should improve Flash performance, out of process plugin provides better stability, and sandboxing with WebKit2 will hopefully improve security but these improvements don't negate the fact that when Adobe was staring a bug straight in their face all they did was go into a state of denial instead of doing something abut it the first time it was reported.
Edited 2010-05-16 03:32 UTC