Is there a specific task that your approach is more suitable to you, flex or js (dojo)?

Good evening everyone.



There is a task to develop a web client for a certain medical referral system, for the most part of its use in IntAnet. The system will have a lot of various components of various functionalities, etc. Communicating with the server via the rest API, session on the client.



Here is a screen of one small part that will be in the system (clickable).



')

One of the assumptions was to take dojo, as one of the most advanced frameworks, but I suggested using flex4 (beta2 at the moment).



From the obvious advantages of the flex:

• Same code rendering in all browsers, regardless of OS, without any hacks inherent in modern typesetting for various browsers
• Powerful AS3 with normal OOP, etc.
• Insanely convenient Flash Catalist (to create fxg code directly from .psd and .ai - that is, in fact, for layout of components on the fly) and Flash Builder 4, with multiple, very wonderful wizards for binding data, etc.
• Convenient flex4 spark components with skins based on graphics primitives and recycled logic from mx components
• Creating an AIR application on the fly from the current code
• After the release of flash player 10.1, it will be possible to use Multi-touch, gestures and, if necessary, use mobile platforms to extend the functionality of the system. At the same time, there is not much need to redo the components for mobile platforms (if at all)
• Wonderful opensource product FlexPMD - tools for automatic review of the code with the ability to use with Hudson, etc., and later will be embedded in FlashBuilder
• Testing code with FlexUnit (adapted from FB4) and testing business logic with automation *
• Convenient debug and profiling code in FB4

Of the minuses:

• Flex4 is in beta. And although the main components are already ready, bugs are possible, etc., but judging by the list of changes from their svn, they fill in a dozen new versions a day, that is, the work is boiling and bugs are corrected very quickly
• Proprietary Flash Player - I personally absolutely do not care for it, but my colleagues have some fears that proprietary might somehow have a negative impact in the future? (such as someone can buy an ad and the player will be bent or something else - although IMHO is absolutely unreal, such as Google will not be tomorrow.)

From myself, of course, in a real web, where the client will not expect an extra second to download a resource, where he has never been, you should not use heavy flex with a long load without need, but for “expected” applications, flex is very cool, not for nothing Raiffeisen released his client bank on a flash (air application).



About js (dojo) in order to avoid disagreements with others, I will not denote the pros and cons - well, the framework as a framework, monstrous, of course, the layout is sometimes questionable even in the main components, but it can be used without problems.



Dear Habravchane, what do you think about this, what technology would you choose if you had a similar task (it is advisable to justify)?