I make web apps for my large company and IE6 is a target platform. My apps have to work even with JavaScript disabled. This means that there are some fairly severe limitations on what I can and cannot do.
However, it turns out that this is probably a good thing (apart from IE's horrible CSS support) because it turns out that users struggle to use applications with complicated interfaces. So I wonder if it's really such a big problem to "dumb down".the UI for enterprise apps...
Welcome to the ranks of the competent. It's amazing how often users are blamed for the pretty but undiscoverable and shoddy work most web authors do. Progressive enhancement should work indefinitely (regardless of flavor-of-the-month client gimmicks) and isn't even that hard.
Why does your organization need IE6? I'm guessing because you've got old apps that were pushing the browser envelope by dipping their toes into MS or other vendor-locked APIs. Fix that, and move on. If you're a decision-maker, just do it. If not, you can't really complain about your fate as a modern, paycheck-collecting Sisyphus.
You don't update a crappy 10-year old browser full of security problems, and yet you let another piece of software (with potentially even more security problems) update itself quietly behind the scenes, totally out of your control?
... and then you actually make your enterprisey software applications depend on that piece of software, which you have little control over?
I just don't get it.
It's no longer that much of an issue though. IE6 is starting to die off in the enterprise space. Once apps get on IE7 they're easier to upgrade thanks to microsoft's backwards compat support in newer IE's. I'm hopeful that IE9 will get adopted more quickly than IE7 and IE8 did.
Flash updates are still a problem unless you use Chrome.
It's true that HTML5 can't do everything that Flex can today. More important is the fact that the vast majority of enterprise apps don't require those things.
Developing an app in Flex just because it can do things today that HTML5 can't is short sighted. That rationale will not hold water 3 years from now when the boss is asking "what the hell is Flex?"
If you consider Flex/AS3 as a DSL for building UIs, the story starts to get more interesting.
It's no big loss to the world of technology if some stubborn backwards company can't have its cake and eat it too. They have to either suck it up or lose enough money to realize that it's important. Flex and similar projects draw out that process. Frankly its a negative for everyone in the long run.
I don't think there is anything that can't be done with HTML5 (the whole stack, I mean), nowadays, and that Flex can do it. Especially since an enterprise can dictate to it's users to use a capable modern browser.
There's plenty a full native solution can do that HTML5, but Flex ain't that, and besides being limited it's also not that rich component-wise anyway.
Or because they're lazy, but they don't like being confronted with the product of their laziness, so if you tell them to upgrade their browsers then they will go to a different company that'll use something like Flex.
I don't think there is anything that can't be done with HTML5 (the whole stack, I mean), nowadays, and that Flex can do it.
Flex can open a direct TCP socket connection. With HTML5, you're stuck with long polling, keep-alives and WebSockets, all of which require HTTP headers and hence can't be used to interface with existing services without a proxy.[1] http://www.adobe.com/devnet/flashplayer/articles/socket_poli...
It's a different way of getting around the security problems, and it's a lot less intrusive than the WebSockets way of sticking an HTTP header in front of the whole thing, which would actually require modifying the server service instead of just running one piece of additional software.
Your first argument is not true. There are things that you can build on top of Flash that you cannot do with HTML5. That list may be shrinking, but this has more to do with Adobe's laziness, rather than the awesome powers of the HTML5 standard that took years to reach a reasonable consensus and even now browsers are struggling to support all of it, with the biggest offender being still IExplorer (surprise).
Your second argument ignores the policy of real-life enterprises. These environments suck, but they are a real problem for developers that want to sell software to them.
Your third argument also ignores why many people like Flex.
Also, this very complaint about being downvoted by Flex fanboys ignores the possibility that you might be wrong in any assertions you've made.
HTML5 is just not a go-er for enterprise products that need a rich UI. Even if it could do everything Flex can (and it can't, yet), you need a modern browser. Many enterprises still use IE6. I'd say 60% of our customers are on IE6; and the remaining 40% use IE7. Demanding IE9 would make an enterprise product dead in the water.
Flex fitted here. You have enterprises who say "no more client server, everything should be web" but then don't give you the web platform to be able to deliver the required user experience (i.e. you must use IE6/7). Flex let you deliver on the web, with a rich UI, on legacy browsers.
So you had a choice:
- Stay on client/server (lots of enterprises won't consider you)
- Develop for HTML5 (not quite prime time, no-one can buy your product as won't work on their browsers)
- Dumb down the UI and deliver in IE6 (workable for some projects, but not for many - some products really do need a rich UI. Especially not doable when porting existing rich client/server app to being webbased - clients don't like backwards steps on the UI)
- Develop in Flex
So it's all well and good saying people yelled 'iceberg' but really you're between a rock and a hard place, and even with this news I'm sure most Flex enterprise developers would make the same decision again - because there really weren't many alternatives.