This post is only the preface to a novel that could be titled "The Devil's Advocate's Guide to Responsive Web Design". The complicated decisions facing those ta

This post is only the preface to a novel that could be titled "The Devil's Advocate's Guide to Responsive Web Design". The complicated decisions facing those tasked with developing and maintaining a responsive site are legion. To start, determine your breakpoints so you can employ the magic of media queries... ...which are neat, but little more than a parlor trick in real world application since serving all the CSS for all possible views is an anti-pattern... ...especially under the currently accepted best practice/mantra of "Mobile First" site development, which dictates initially assuming a visitor is on a smartphone (to achieve the fastest response for the weakest use case, i.e., relatively low power device+high latency/unstable network) then dynamically scale the content/features based on client capabilities... ...requiring a solution for feature testing and/or device detection, which is performance overhead somewhere in the stack and, though evolving quickly, will remain a elusive target for the foreseeable future... ...which THEN means (just as the OP says) you aren't really developing, maintaining, and serving a single responsive site but one of 3 or more variations which, depending on who you ask, should have context appropriate content. What's that? You have a highly-performing, flex grid-based, sugar-coated wonderland of a site? Tell me how efficient your responsive/adaptive image workflow/solution is... TL;DR Thank you @beep for the job security. ;)