Nice to see people speaking about their development experiences, ecspecially when using AJAX & Flash together, something that makes absolutely no frikin’ sense to me. This gives a great insight into how people who are not Flash devs expect to use Flash, and how they expect it to work in their project flow. Fascinating stuff.
Since I’m a Flasher at heart, I must respond to his points.
Sockets: XMLSocket is an alternative to Flashcom. It’s been in Flash since 5, and like AJAX’s XMLHTTPRequest, both send and receive XML strings, except XMLSocket in Flash is a persistent socket and allows for server-push instead of the simple request/response. There are a lot of free & professional socket servers out there for this, EXTREMELY cheaper than Flashcom, ecspecially Flashcom 2 since that pricing model doesn’t really facilitate data-only applications anymore.
Additionally, Flash Player 8.5 has binary sockets built-in; expect existing binary socket servers to see a re-surgence in use, and new ones built just for Flash server alternatives.
I will agree, though, that Flash has it’s code too tightly meshed to the GUI; Flex is indeed faster for prototyping form based applications, and the flexbility has increased 10 fold since your code is not tied to how you lay out your GUI.
Text handling: While I agree text usability in Flash blows, mainly from an integration standpoint, it’s rendering rocks. If you use device fonts, it is extremely readable, even at lower font sizes (14 and below). Unfortunately, the IDE’s default behavior is to use embedded fonts, which has lead to the “Flash shows blurry fonts” impression, which unfortunately is the fault of developers, not the technology. Additionally Flash Player 8’s font rendering engine rivals that of PDF, even with small font sizes.
Again, it’s really great to read these types of articles; both from the AJAX dev comparisons to getting insight into how developers use the tools & their expectations of them.