> Perhaps its the apparent conflict between UX and DX that leads to tooling complexity? In theory improved DX leads to improved UX. In practice, subpar/lazy to

> Perhaps its the apparent conflict between UX and DX that leads to tooling complexity? In theory improved DX leads to improved UX. In practice, subpar/lazy tooling needs to be worked around to get better DX. I’ve added a lot of JS weight to migrate legacy apps to React always improving time to interactive and responsive error handling/messaging. Vanilla JS and even Jquery just don’t have the DX that allows them to scale in a corporate context (specifically because of under experienced engineers and poor “due dates”). IMO it’s a lack of initiative from browser developers to move the web forward faster (obvious given the funding comes roughly exclusively from the developers of iOS and Android). I understand the inertia of legacy browsers, but it should not take decades to eliminate the need for these DX polyfills (eg like Jquery took to become redundant, and how long it’s taking React/Vue/Svelte style components).