Adobe Not Playing Nice On Flex Bugs
Today, I shall tell a story about bad bug handling from Adobe on the flex framework. A story about Adobe pushing their payware LCDS product, as a solution to a bug in flex or flash!
A while ago, I posted on flash still being closed and proprietary, to make us think about that, before blindly adopting flex as a cool way to do RIAs. That post also resulted in InfoQ publishing an article, where they asked if the proprietary nature of the flash player is keeping us from using flex. I also got a, mildly interesting, comment from John Dowdell from Adobe, stating that the player team is “responsive”, which should make up for it not being open.
It turns out, that it really does matter, how open the source and proces is.
Have a look at this flex bug SDK-13765 (which you sadly cannot vote for anymore, because it is closed by Adobe). It is about how the information in a SOAP Fault (the result of a failing web service call) response isn’t shown or accessible to the flex client code doing the web service call. Now, this is just a bug, which of course should just be fixed.
But hey, what is Adobes “solution”?
They mark it as “Closed”, with the resolution “Not a bug”. There is no information whatsoever in that bug, on why this is not a bug. There is a sole comment from Adobes Bill Sahlas, stating that you need to buy Adobes LCDS product, to get around this bug.
What’s more is, that this bug 13765 is actually a duplicate, which was reentered in the bug system, because Adobe closed the original bug 11841, also without solving the issue. Since then, it seems Adobe has made the old bug votable again, but there is no good information about where the problem lies, and why they won’t fix it. Come on Adobe, this is just not good enough!
BTW: The parts of flex, that the bug most likely lies within, is not open sourced…
February 5, 2008
В· 
polesen В· 
One Comment
Tags: adobe, flash, flex В· Posted in: Rich Internet Applications, Uncategorized
One Response
Hey, you’re not the only one getting screwed. http://ducktyper.com/2008/1/17/socket-output-progress-in-air
These guys suck. Making people who boss computers around all day feel helpless probably isn’t the best thing to do to promote good associations with their development platforms.
Leave a Reply