The problem in this case is that your suggestion does not work for at least one known use case for the site: viewing from a text-based browser (such as eLinks, Links, or others).
I wonder how many of the users here actually view this site from a text-based browser. Probably I can count them on one hand.
unless specifically directed to do so
If they do everything they can to view this page from a text-based browser when literally every OS on the planet nowadays comes with a GUI, then doing a simple wget gif-image is not going to hurt them at all. And this change wouldn't disable the entire site for them. They would still be able to use the site, except they wouldn't be able to vote as conveniently as the rest of us. But if someone is concerned about bandwidth, then this would cut down a big amount.
Now, if you wanted to go the extra mile, it would be possible to transform the site so that individual posts are loaded separately and are cached in the user's localStorage, which provides about 5MB to 10MB of space per website. So, the most popular or most viewed posts could be stored there when the visitor requests them, so when the visitor clicks around, the same posts wouldn't have to be downloaded over and over again. But then we're involving JavaScript too, so that eliminates another set of users whose browser has JS disabled. :P
In reply to Re^2: New Design for Sending + - votes on PerlMonks
by harangzsolt33
in thread New Design for Sending + - votes on PerlMonks
by harangzsolt33
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |