我一直在问一个金融服务客户，使该技术栈将用于重新设计他们的web交付界面的建议。该客户端建立所使用的顾问来分析其客户的投资组合，做出明智的交易决策和管理的例外pre定义的产品组合范围（例如，增持股票等）的软件产品。某些分析包括性能等图表但没有过于复杂，将必要的大量的图形或图表库。

我倾向于推荐HTML，CSS和JavaScript（特别是jQuery的），由于架构，编码实例丰富，并招募人才队伍，以实现和管理在现有基础上的能力的开放性。不过，我想一个人玩魔鬼代言人（如果可能的话），并认为我为什么要重新考虑，并提出了Flex。我的直觉加固也是欢迎的。

一些潜在有用的信息：

数据后端是Java的春天对/顶基于与Hibernate一起使用。

跨浏览器的支持并不需要是广泛的，与B2C的接口，也就是说，它是完全没有为我们规定，这是支持IE和Firefox的唯一的（虽然我会preFER Chrome浏览器，Safari浏览器等所有的工作）

我们的一个开发者诟病的Flex不能够本地处理由Web服务返回的XML。我并没有效仿的榜样，但他解释说，在前端需要后端的对象发生了变化，每次重新编译/有田补充道。

目前的开发团队有很强的Java技能，所以也许第三个解决方案（谷歌的网页工具包？）应该被考虑。

我只是想指出，就在＃3，有关开发商在说谎。 Flash并处理XML本身没有问题。如果XML变化和你硬codeD在你的应用程序的路径，你就必须重建，但同样的，你就必须改变JS code和重新部署。

VS HTML / CSS / JS的Flex之间的争论是一个将永远继续下去。我已经做了两个，这真的取决于你要完成的任务。我也是在金融行业，我会告诉你，这个从我所看到的：那已不重要近来任何Web项目已全部完成的Flex 。我们说的是非常非常大的项目囊括众多数十人。这样做的原因是，Flex是面向对象的，在Eclipse中（这样你就可以的Java / Flex的的，如果你想要做既没有概率切换），可以彻底测试（单元，用户界面​​，集成）一个IDE，以及支持使用Maven （的Flexmojos），拥有企业级框架摆（香菜，Robotlegs的，Swiz;东西仍然缺乏JS），具有很大的主题化的支持，实时数据支持的（非常金融重要的），组件库（premade，更少的工作），以及良好的库支持（需要在所有的大型项目），每一个浏览器将显示它完全相同的方式。此外，闪存正在成为越来越突出的手机，你可以随时重复使用code和重新编译为Android，剧本和iOS。

随着中说，JavaScript是不坏。我爱CSS3和它的能力，哪些HTML5将带来的，但浏览器之间的支持是乏善可陈的最好的。很大的原因就是许多使用HTML / JS / CSS是因为你可以把它移动在一个瞬间可用。我通常使用JavaScript较小的项目，因为它的维护更少，更容易启动（一个或两个开发人员最多，也许是设计师），并且不需要插件。我也注意到，Javascript和Flex的开发之间的时间是因为调试（Flex的考虑更少的时间）非常不同的。

显然，你必须权衡这两个，看看什么最适合。我喜欢把我自己的技术无关，但我也是一个现实主义者。与Flex项目，我已经做了，这将是不可能创造一个完美的Javascript等效的，因为让我们面对现实是，HTML5尚未敲定，只有最新最好的浏览器都支持它（而不是的所有的其任）。

I've been asked by a financial services client to make a recommendation for the technology stack that will be used to redesign their web-delivered interface. This client builds a software product that is used by advisors to analyze their clients' portfolios, make informed trading decisions, and manage exceptions to pre-defined portfolio bounds (e.g., overweight on equities, etc.). Some of the analytics include graphs of performance, etc. but none are overly complicated that would necessitate an extensive graphics or charting library.

I'm leaning towards recommending HTML, CSS, and JavaScript (specifically jQuery) due to the openness of the architecture, the abundance of coding examples, and the ability to recruit a talented team to implement and manage on an ongoing basis. However, I'd like someone to play "devil's advocate" (if possible) and argue why I should reconsider and suggest Flex. Reinforcement of my gut feel is also welcome :)

Some potentially useful information:

The data backend is Java Spring on top of/in conjunction with Hibernate based.

Cross browser support does not need to be as extensive as with a B2C interface, i.e., it is perfectly fine for us to dictate "this only is supported on IE and Firefox" (though I would prefer Chrome, Safari, etc. all work)

One of our developers criticized Flex for not being able to natively handle XML returned by a web service. I didn't follow the example, but he explained that the front-end would need to be recompiled each time the back-end objects were changed/had fields added.

The current development team has very strong Java skills, so perhaps a third solution (Google's Web Toolkit?) should be considered.

I just want to point out right away at #3 that the developer in question is lying. Flash does handle XML natively no problem. If the xml changes and you hard-coded the path in your application, you would have to rebuild, but the same, you would have to change the JS code and redeploy.

The debate between Flex vs HTML/CSS/JS is one that will go on forever. I've done both and it really depends what you're trying to accomplish. I'm also in the financial industry and I will tell you this from what I've seen: any web project that has been important in recent times have all been done in Flex. We're talking very very large project encompassing many dozens of people. The reason for this is that Flex is object oriented, has an IDE in Eclipse (so you can switch between Java/Flex if you wanna do both no prob), can be tested thoroughly (unit, UI, integration), well supported with Maven (FlexMojos), has a slew of enterprise level frameworks (Parsley, RobotLegs, Swiz; something still lacking in JS), has great theming support, real time data support (very important in finance), component library (premade, less work), and good library support (needed in all large projects) and every browser will show it exactly the same way. Plus, Flash is becoming more and more prominent on mobile and you can always reuse code and recompile for Android, Playbook and iOS.

With that said, Javascript isn't bad. I love CSS3 and what it's capable of and what HTML5 will bring, but the support between browsers is lackluster at best. The big reason why many uses html/js/css is because you can make it available on mobile in a jiffy. I normally use javascript for smaller project because it's less maintenance, easier to start (one or two developers max, maybe a designer), and doesn't need the plugin. I've also noticed that development time between Javascript and Flex is very different because of debugging (Flex taking less time).

Obviously, you'll have to weigh both of these and see what fits best. I like to think as myself as technology agnostic, but I'm also a realist. With the Flex projects I've done, it would of been impossible to create a perfect Javascript equivalent because let's face is, HTML5 isn't finalized and only the latest and greatest browsers support it (and not all of it either).