Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I've evaluated Flex and GWT, and for our project at least we chose to go with Flex. Using BlazeDS for the integration with Java made things VERY fast, there are many charts you can find on the internet that'll give you a hint about how much faster, and that was one of our main criteria. Even dealing directly with XML, Flex was about an order of magnitude faster than GWT when it came to getting data back and forth from client to server, and BlazeDS made it much faster. I think it boils down to Flex clients are running in the Flash VM, and GWT is running in the Javascript interpreter. If you're running in Chrome the performance might be close, I don't know, but if you aren't running Chrome I think the performance is solidly in the Flex corner. I have done JSON in Flex, there area couple of libraries to let you do that on json.org. There is also a "History" library in Flex/Actionscript that allows you to handle back button issues. All in all, they are both great solutions, if you need to support platforms that don't support Flash, then GWT is the obvious choice, but otherwise I can say we have a very successful Flex app using Java/Spring/Hibernate on the backend via BlazeDS supporting hundreds of simultaneous users with speeds that are very favorably comparable with desktop client/server application speeds.</p> <p>I'll add some background here. We were charged with replacing a Windows Client/Server application with something that would be roughly comparable in performance, much more configurable, have no configuration on the desktop, and be a "web application". We kicked around Java applets, .Net 1 click installs, GWT, and Flex. Based on a balance of ease of use, performance, the fact that we have other reasons to require Flash on our users desktops, and frankly political reasons, (java haters ;) we chose a modular Flex application. Now more than a year later, and 90+ dynamically configured modules based on user roles, I think it was pretty successful.</p> <p>But, of course, YMMV ;)</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload