Linked by Thom Holwerda on Thu 11th Mar 2010 22:59 UTC
Permalink for comment 413436
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
More News »
Sponsored Links



Member since:
2005-07-06
Bullcrap; when they shipped 10.0 they knew about the bug and claimed that development was too far along to fix it up; many updates over the 18 months since its release and not a single one of them addressed the bug. So please, stop the crap - Adobe knew they were shipping a product with a known crash bug and for 18 months chose to do nothing about it just like they could do something about the appalling CPU hogging of Flash but instead decides to blame everyone else for their incompetency.
Adobe should be thanking their lucky stars for the fact that if it weren't for Microsoft's stupid stance of not providing Silverlight development tools for Mac - Flash would have been strangled and left for dead by most developers years ago.
Edited 2010-03-12 19:52 UTC