3 ms·

For some reason this article received a fair amount of negative feedback here. I quite enjoyed it. It's good to remind developers that they should ensure that

by Ianvdl 11y ago

For some reason this article received a fair amount of negative feedback here. I quite enjoyed it. It's good to remind developers that they should ensure that their products degrade gracefully, and to give a few examples of what could go wrong. Mentioning the (somewhat basic, but still generally effective) fault-tolerance of HTML/CSS vs JS along with the user's basic viewpoint also helps to get his point across further. Maybe I'm just used to reading longer form content, but I didn't feel that this brief blog post was a waste of time.

mmcclure 11y ago
> It's good to remind developers that they should ensure that their products degrade gracefully I agree! I don't think it's a bad reminder, I think it just rubbed me the wrong way that he seems to present this whole concept like something new and novel, when frankly, it's just...not. The entire blog post doesn't have a single mention of either "graceful degradation" or "progressive enhancement," both of which would be useful to hear if a reader wasn't familiar and wanted to learn more about this topic.