Yes you bring up an important point - namely there are public websites and services that also do cool things, that need to focus on standards compliance and SEO and everything. These over time will become a best fit for HTML5 if they aren't already. Flex isn't great for SEO.
Then there are applications, that are simply programs which happen to use the browser as a delivery mechanism, where generally the entity writing the application also controls the browser or computer being used to use the application. Sometimes they are called "enterprise applications" but I don't think this categorisation is true in all cases. They are really a different kettle of fish and more often a good fit to Flex. John 2011/11/18 Angelo Anolin <angelo_ano...@yahoo.com> > ** > > > 95% of organizations and businesses bottom line is to be able to deliver > projects and applications with the least amount of time and budget. > > We are able to deliver software faster, better and more responsive using > Flex/Flash technology running on the web than any other implementation out > there. > > I think Adobe forgot to mention that enterprise grade applications are far > different from fancy web sites powered by HTML5, CSS, JS, etc.. > > Bottom line is if you are able to deliver software better, and you have > very satisfied users, use that technology. > > Just read this post and somehow rings true.. > http://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-programmer/ > > ------------------------------ > *From:* Tomislav <i...@svemir.net> > *To:* email@example.com > *Sent:* Wednesday, November 16, 2011 6:08:58 AM > *Subject:* [flexcoders] Re: Why Flex now? > > > That statement is updated today. Checkout the same link: > http://blogs.adobe.com/flex/2011/11/your-questions-about-flex.html > > --- In firstname.lastname@example.org, Rick Schmitty <flexcode@...> wrote: > > > > I've been a Flex developer since it's first beta however many years ago. > > Today I just saw this response from Adobe: > > http://blogs.adobe.com/flex/2011/11/your-questions-about-flex.html > > > > > > *Does Adobe recommend we use Flex or HTML5 for our enterprise application > > > development? > > > *In the long-term, *we believe HTML5 will be the best technology for > > > enterprise application development*. We also know that, currently, Flex > > > has clear benefits for large-scale client projects typically associated > > > with desktop application profiles. > > > Given our experiences innovating on Flex, we are extremely well > positioned > > > to positively contribute to the advancement of HTML5 development, > starting > > > with mobile applications. In fact, *many of the engineers and product > > > managers who worked on Flex SDK will be moving to work on our HTML > efforts > > > *. We will continue making significant contributions to open web > > > technologies like WebKit & jQuery, advance the development of PhoneGap > and > > > create new tools that solve the challenges developers face when > building > > > applications with HTML5. > > > > > > Emphasis mine. If anyone has followed any game or application development > > where 'many members' of the team are switched to the next greatest thing, > > that normally means there are few maintenance developers for the existing > > product and not much new innovation to it. The company wants its best and > > brightest working on its future, not supporting its past. > > > > Combine that with the facts that Adobe bought PhoneGap and released Edge > > preview. It's not hard to put all these facts together and see that long > > term they want an IDE & framework for app development in HTML5. Perhaps > > Flex5 will be an HTML5 version of Flex as they start putting together > html5 > > components > > > > > > Outside of "having to support IE6" why would you choose to start a > project > > in Flex today? > > > > > > >