One of the most painful aspects of working with front end scripting (IMO) is having to deal with the browser differences and devoting a large chunk of time writing code in such a way to deal with these differences, and then having to perform tests across multiple browsers to make sure it works consistently as expected.
Was my observation correct? If not, what platform issues will still need to be considered when utilizing Flex?
Also, not that I'm a performance nazi, but I'm sure there must be a certain level of degradation of performance running in this capacity? I've perused various Flex driven sites and some have been painfully sluggish, but I'm not sure if this was a case of the designer just cramming too much whizzy features on one page and/or there was network access issues that influenced this performance since as others seem to work responsively. Of course it would seem difficult to perform a benchmark that could accurately show an apples to apples comparison to other browser UI frameworks.
Oh, one more thing. Has anyone here tried the Flex 3 plugin for Netbeans 6.5? Observations?
Flex applications are rendered and executed inside Flash Player and in all browsers the Flash Player is installed as a plug-in. Flash Player has been developed and tested across multiple OS/Browser combinations for consistent in behavior and performance, and in most application you don’t really need to worry about cross browser support issue since Flash Player takes care of it. However there are few areas where Flash Player still depends on client machine’s hardware capacity one of it for using hardware-acceleration and for hardware-accelerated scaling to work, you need certain hardware configuration see (http://www.macromedia.com/support/documentation/en/flashplayer/help/help01.html#117103). And this is the one you might need to consider while developing Flex application that utilizes hardware-acceleration for Video playback or Image rendering.