>I hope the services I want to use (will) have a non-browser API (eg Twitter).
although it uses http, twitter has got an api that you can use outside a browser. it's much the same with several others, including aws. there are reasonably clear descriptions of the messages, and you can construct and send them however you like, in which ever language you like. in fact, since a browser must ultimately send messages, it's not clear what a `browser API' would look like. the closest is probably something that's expressed only in terms of javascript invoking some secret code hidden in a binary module running within the browser, making it hard to work out easily what the messages are (if they're binary) or how they are formed (whether binary or text). on the internet, no one can hear you scream when someone yet again invents `the browser as operating system'.
