In some ways I can only agree, having criticised others for apparently doing the same thing. I guess the difference is that it was completely bloody unnecessary to waste enormous amounts of bandwidth for the cost of just a little bit of basic checking. For me individually, bandwidth is virtually free, for others it is metered (not everywhere has Western-levels of Internetz). But bandwidth is not free – multiply up 49.2 MB by a number of expected page visits.
So, as a matter of principle we need to stop acting as if resources are free. Also if the author couldn't even get that simple HTML detail right then it potentially says something about the quality of his site's information. Perhaps.
> Also if the author couldn't even get that simple HTML detail right then it potentially says something about the quality of his site's information. Perhaps.
Perhaps is doing some heavy lifting here. I take it from the fact that the lectures are on Functional Programming that OP might not be a front-end developer and might not have the level of care needed for front end to compress the images in a way that renders nicely. So,
Perhaps you ought not judge someone releasing their free teaching materials for a backend class on their front end development, when the site is a centered <div> with purely static elements.
Perhaps you ought to slow down and do some critical thinking before being critical of others.
I'm a back-end dev (inc. FP) and RDBMS guy and even I'd know not to do this; instead to pre-shrink images presented as decorative thumbnails. But let's be constructive, what form should my critical thinking have taken, how should I have done better (edit: or criticised more carefully)? Serious question. Thanks.
As a matter of principle, those in bandwidth-constrained situations should be browsing via proxies or browsers that automatically compress, such as Opera Mobile back in the day, or Google’s more modern compression baked in to Android/Chrome. (If it still exists, it’s been awhile…) That said… yeah, it couldn’t hurt to put a free CloudFlare CDN in front with automatic image optimization, for example.
> "it was completely bloody unnecessary to waste enormous amounts of bandwidth"
Thats not enough. It was completely bloody unnecessary to waste enormous amounts of co2.
And critical thinking should lead to the realization that not many people have to solve the - albeit small - mistake of an individual via Cloudflare or similar, but rather someone should do it correctly right away. And if he has no knowledge of frontend, he should not do things he has no knowledge of.
So, as a matter of principle we need to stop acting as if resources are free. Also if the author couldn't even get that simple HTML detail right then it potentially says something about the quality of his site's information. Perhaps.