The web browser has been the dominant thin client, now rich client, for almost two decades, but can it compete with a new thin client that makes better technical choices and avoids the glacial standards process? I don't think so, as the current web technology stack of HTML/Javascript/Flash has accumulated so many bad decisions over the years that it's ripe for a clean sheet redesign to wipe it out.
Permalink for comment 377997
To read all comments associated with this story, please click here.
A typical HTML page contains almost entirely text. Not markup - text. Content. That wouldn't change just because you're using a binary format, that binary format would still contain large amounts of text.
The solution? Compress it!
Then you end up with a compressed text format, and a compressed binary format, which are about equal in size. Both are easily machine-readable. Only one is human-readable. Simply using a binary format is not going to make the tools magically better, so you're really not going to get any better tools than we have now.
Member since:
2007-09-08
Why would you not compress the binary format?
A typical HTML page contains almost entirely text. Not markup - text. Content. That wouldn't change just because you're using a binary format, that binary format would still contain large amounts of text.
The solution? Compress it!
Then you end up with a compressed text format, and a compressed binary format, which are about equal in size. Both are easily machine-readable. Only one is human-readable. Simply using a binary format is not going to make the tools magically better, so you're really not going to get any better tools than we have now.