there's still lot of churn coming from following a moving target. like when ios made the top of the page untouchable least it pulled safari out of full screen,

there's still lot of churn coming from following a moving target. like when ios made the top of the page untouchable least it pulled safari out of full screen, breaking the toolbar convention of the past two decades. and when ios made the bottom of the page untouchable least it pulled safari out of fullscreen, breaking the bottom bar icon webapp did under the very apple guidelines > https://developer.apple.com/ios/human-interface-guidelines/bars/tab-bars/ https://developer.apple.com/ios/human-interface-guidelines/b... and when ios made the app sides unusable due to a varying notch, having a whole set of unstandard properties you have to handle to manage correctly being into safari on a iphone x if we had companies following standard decently and a linear, planned grow instead of the organic mess we're into, it'd be far easier to produce building blocks that work in a stable manner over time. we're better today than in netscape days, but marginally. as complexity increase the cost of this constant churn does too and the saving from better framework are not quite enough to offset the constant fads that come and go.