All of this is built upon the misguided premise that the same markup could work both for mobile and for desktop. It can't unless it's text and images only. Different interaction paradigms call for different positioning of elements, different nesting, different density, etc. You do really have to have two sets of templates if you want to support mobile devices.
> Different interaction paradigms call for different positioning of elements, different nesting, different density, etc.
I’ve challenged this on HN before, but I’ll take a different approach. Can you describe a scenario where these fundamentally can’t be achieved with the same markup? I’ve never encountered one, in over a decade of developing responsive apps and sites.
They maybe can be done with the same markup, but it'd be much more work and some duplication, too. And of course it's absolutely unacceptable to redesign your UIs to make it easier to reuse markup — remember, developer experience doesn't matter if the end result is shit.
