Thursday, December 15th, 2005p>Fellow Ajaxian Michael Mahemoff posted on something not discussed enough – what Ajax can’t do:
- Browser morphing Adding buttons, toolbars, bookmarks, icons; changing browser behaviour.
- Local file access Reading and writing files on the user’s hard drive.
- Sound Playing music and sound effects.
- Rich graphics Providing rich graphics, changing dynamically. (This is gradually changing with the introduction of SVG in some browsers, but it’s no match for desktop graphics.)
- Keyboard shortcuts Providing a full range of keyboard shortcuts while avoiding conflicts with the browser’s own keyboard shortcuts.
- Hardware access Input from devices such as microphones, webcams, and gamepads; output to devices like printers and portable gadgets.
- Extended communication Communication from the client machine to locations beyond just the base server, and in protcols other than plain old HTTP.
- Operating system interaction Catching events such as shutdown initiation; changing preferences; popping up alerts; reading hardware information.
Of course, we’ve seen a bunch of possible solutions to the local storage issue. I fear we won’t have a reliable, non-hack solution unless the IE team and Mozilla team can just meet and agree on it. The limitation in changing browser behavior and shortcut keys is also an advantage in some ways, as it keeps everything nice and standard between apps.
What other things can’t (or shouldn’t) ajax do?
Posted by Rob Sanheim at 10:28 am