3 ms·
Assume adobe released a hardware platform and it didn't support javascript. If somebody were to suggest that the entire web development community was going to
by blhack 17y ago
Assume adobe released a hardware platform and it didn't support javascript. If somebody were to suggest that the entire web development community was going to abandon javascript in order to allow adobe's platform to reach the saturation required to make it the "standard", then your argument might make sense.
As it stands, the iPad exists in a state that makes it almost unusable for the overwhelming majority of web users (at least as anything more than a novelty, much like web browsing on the iPhone)
- glhaynes 17y agoPerhaps unusable as their only machine. That by no means makes it merely a novelty.
- Tichy 17y agoBut it makes it useless as "the computer for mom".
- glhaynes 17y agoI was responding to a claim that the iPad is "almost unusable for the overwhelming majority of web users (at least as anything more than a novelty [...])". If mom's savvy enough to use a computer aside from her iPad then she can use that computer to get to the sites she wants to go to that her iPad doesn't support. If she's only savvy enough for an iPad, then she's still better off being able to get to the non-Flash parts of the web than nothing.
- sesqu 17y agoGraceful degradation. People would absolutely suggest that, and charge dearly for implementing it. Companies would pay for some of it, and in 5 years, it would either die out or there would be some sort of "cgi on rails"-framework that automates some minimal version of that, that looks horrendous and sorta-kinda works. Probably ASP.net. Then we'd have hobbyists and ux professionals hand-crafting everything on a lamp-like stack, and everyone else would get along with upgrading backends. ECMAScript may be google's horse in the race, but it's still just an add-on.