If you’re even remotely involved with Flex development, you’ve likely heard about this issue. You’re probably sick of hearing about it, just like I am. Fortunately, the issue will be effectively closed in the coming days. Adobe has stated that they intend to make a final decision this week. That being the case, I am making one final statement on the issue.

You don’t have to look hard to know that the community overwhelmingly hates Adobe’s proposed decision to prefix the name of new components with Fx. FxButton, FxCheckBox, FxResize (yes, effects too), etc.

The technical aspects have been covered ad nauseum and I don’t intend to rehash them all here. There is nothing technical in nature forcing Adobe to prefix the class names. Its really not even that tough of a problem and, as others have pointed out, the Flex team is a large group of extremely smart people. I think its pretty obvious this issue stems from a push from the business side of Adobe that wants a new product released in a certain timeframe in order to drive revenue. I completely understand this and don’t fault them for it one bit. Flex is Adobe’s product and they can do with it as they please but if they start making decisions that sacrifice aesthetics, readability and architectural purity, it will be a product I have much less desire to use. I know I’m not alone in feeling this way, so make sure you let Adobe know what you think.