Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <ul> <li>Vendor lock-in... Using supposedly "standard" web techs you are still locked in to whatever JS framework tool you choose. What's the difference?</li> </ul> </blockquote> <p>Adobe is a for-profit company, so they theoretically could have a real interest in making it difficult for their customers to move to a different platform.</p> <p>JavaScript frameworks are written by volunteers, often to solve problems they have writing apps in JavaScript. There isn’t the same motivation for framework authors to make their users lives difficult.</p> <p>Equally, Adobe <em>own</em> Flash and Flex, like Microsoft owns Silverlight. No-one <em>owns</em> JavaScript, CSS and HTML. They’re controlled by several companies working together in standards bodies. So they seem safer to rely on, because no single company can move them in a direction that’ll hurt others.</p> <blockquote> <ul> <li>It's even worse because the heavy competition between the multitude of "AJAX frameworks" means your FW of choice is more likely to be abandoned some day.</li> </ul> </blockquote> <p>But it’s better, because JavaScript frameworks are written in JavaScript, so if your framework did get abandoned, you can adopt it, or rewrite your own. JavaScript frameworks aren’t as complex as something like Flash.</p> <blockquote> <p>Search engine indexing... this is a problem for web-SITES, not web applications: two entirely different things.</p> </blockquote> <p>That’s debatable.</p> <blockquote> <p>deep-linking is not a problem for a Flash app, even basic research can dispel that myth.</p> </blockquote> <p>Could you point to a reference? (I’m not disputing it, it’d just be good to have a reference.)</p> <blockquote> <p>What is the difference between the software and hardware world where they are adopting virtualization technologies so readily?</p> </blockquote> <p>I don’t really see what problem virtualization solves with regards to browser application interfaces. </p>
    singulars
    1. This table or related slice is empty.
    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. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COBut also "theoretically" Flex can integrate with most anything you can think of, Adobe is much more OSS friendly than most companies, and the main problem people have with 'proprietary' is that it's proprietary. JS frameworks are written by volunteers--this is the problem. Volunteers have other things to do, they get bored, move onto other 'free' projects, may get tired of fixing the problems in their 1990's JavaScript code after years of adapting to new browsers. And I really feel bad for you if you have to resort to maintaining your own AJAX framework--good luck explaining that to mgmt.
      singulars
    2. COThis "but it's for-profit!" (it's not, anyway) thing has to die. For profit is not bad. It provides motivation for better customer service. Virtualization doesn't solve the interface problem (a problem JS scripts also have), it solves all the other problems such as O&M costs, platform incompatibility (other than interface related), development/testing cost due to having to target 5 different browsers, etc. You can also run a Flex application outside of a browser as a desktop app quite easily. Deep linking http://www.adobe.com/livedocs/flex/3/html/help.html?content=deep_linking_2.html
      singulars
    3. COOn the proprietary versus volunteer thing, I’m with you on “for profit” not being inherently bad. I’m just saying that with a framework like jQuery, even if everyone in the world suddenly lost interest in it, you can fix stuff yourself, whereas if Adobe decided that Flex wasn’t worth the effort, that’d be it. Re virtualisation, I see your point now, having one environment to target is a big time-saver. (Although, ironically, the deep linking page you linked to contains the phrase “Deep linking only works with certain browsers.”)
      singulars
 

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