With webassembly and webgl, why do browsers need to evolve? If you want some feature the browser doesn’t provide, just make it yourself and draw it onto the canvas. x86 assembly gets occasional performance improving instructions but fundamally it’s existed for 50 years and can continue to support all modern programs. X11 survived for 40 years before any talk of a replacement really appeared. Why can’t Chrome be maintenance only for 40 years and let apps and websites innovate on top of its primitives?
To make web development a more consistent experience?
To make it easier for developers to build a more accessible web for users with certain impairment? Without needing to re-invent the wheel with thousands of lines of JavaScript or write Web Assembly (i am not even sure how to build an accessible input element with canvas that work with screen reader, keybroad focus etc, this is crazy)?
On desktop, questions like how to make an accessible input element are handled by your widget toolkit. Why does the browser need to handle every question itself? Let the qt or gtk or whatever folks answer the question of how to create an accessible input element. Split the scope and investment among many players which individually don’t need as much funding and can innovate more quickly.
With webassembly and webgl, why do browsers need to evolve? If you want some feature the browser doesn’t provide, just make it yourself and draw it onto the canvas. x86 assembly gets occasional performance improving instructions but fundamally it’s existed for 50 years and can continue to support all modern programs. X11 survived for 40 years before any talk of a replacement really appeared. Why can’t Chrome be maintenance only for 40 years and let apps and websites innovate on top of its primitives?
To make web development a more consistent experience?
To make it easier for developers to build a more accessible web for users with certain impairment? Without needing to re-invent the wheel with thousands of lines of JavaScript or write Web Assembly (i am not even sure how to build an accessible input element with canvas that work with screen reader, keybroad focus etc, this is crazy)?
On desktop, questions like how to make an accessible input element are handled by your widget toolkit. Why does the browser need to handle every question itself? Let the qt or gtk or whatever folks answer the question of how to create an accessible input element. Split the scope and investment among many players which individually don’t need as much funding and can innovate more quickly.