3 ms·

This doesn't answer the question of why Adobe doesn't do that, it lists the things that Adobe could step up to do. Yes, we know there is no ready-made IDE like

This doesn't answer the question of why Adobe doesn't do that, it lists the things that Adobe could step up to do. Yes, we know there is no ready-made IDE like Adobe's Flash IDE: fixing this problem is something Adobe can do, by providing a ready made HTML5 IDE. Why isn't Adobe doing that and leading the charge? There are distinct problems with HTML5 replacing Flash, and Adobe is in a unique position to partner, consult, contract, and contribute to that. For example, if everyone else's javascript VMs are crap and Adobe's Flash interpreter (which is close to javascript, isn't it?) is awesome, then Adobe can help contribute rather than taking a beating from industry leaders (Jobs) and be part of the solution rather than be viewed as part of the problem.

nanairo 16y ago
I think the answer is a common one in free markets: cost. Adobe would need to invest a _lot_ to make a good HTML5 IDE, and what would they get then? At best they'd be in the same situation as they were before just with HTML5 instead of Flash, and on top of that they would have lost control of the platform. So the bean counters find this kind of proposition difficult to swallow. And if you say: but what if someone else did? Then they'll reply: well, then make sure Flash kills anything HTML5 related, and that's how they end up putting a lot of money to preserve the status quo, instead of using their baskets full of gold to make them run faster.