Makes sense.
I was more thinking in terms of flexibility for the developer.
So a dev can choose to do multiple views, or just offer one.
Which could also mean for a bits enabled, mobile enabled, extension, I don’t need to do a feature flag check, as Twitch already detected and determined to deliver the mobile/bits off html and (and thus I load the js) code. Which then means a smaller file and less data over the wire.
But I do see how this could lead to over complication.
Perhaps an alternative to JS feature flag check is more Query string arguments? But then theres no intelligence in the HTML itself to perform switches, and now we are err-ing towards some sort of HTML templating akin to Pug/Jade under NodeJS for example.
I’m probably thinking too much into the Speed/Over The Wire file size for mobile