From what i understood, the
only rational argument I saw on /. likened the problem of increased quality or bandwidth to that of websafe graphics.
Though still reaching a
different conclusion to me.
I still remember the discussion behind websafe colours, back then people thought nobody really needed something better, had or would get it, nor the use, and if they did, could similarly deal with the inconvenience. That, along with the question of support, has since been solved.
This assumption hinges on two things, that
- people who need extra are technical, and that
- technical users use their skills to ability.
Knowing the skill required isn't for everyone, its a backend problem, which makes it a very top-down question, instead we could even the playing-field.
I would much rather (as a technical user) just put up the source /(best) image I got, and let scaling and quality be left to ability of the users software, without having to make assumptions.
I want to be that user too, on a general basis, the technical part of me cares even more about having the ability. Don't compress quality.
My assumptions on the backend, when I'm just doing something else, will always be limited, or it will become an incomprehensible problem to deal with, with fallbacks and different methods etc, and even then, it still gets outdated.
In total, for however much better the total sum of bandwidth has gotten, we seem to still be able to use it up.
That is a net gain for everyone.
You cant look a gift horse in the mouth if you don't understand the difference between a horse and a trojan.
I've been rewriting the page to try and help wb make the points he put in. There should be something about rendering time too.