The web is dying under chrome, with the excuse that iOS has its responsibility in the stale doesn't help either.
It's dying, not because of vendors pushing their favorite flavor, but because it has a terrible, horrible API, that make building an app with tightly controller Ui and Ux atop of it a Sisyph-ian challenge.
It's horrible for 3 key points reasons:
- the insistance that the document oriented API (DOM/HTML) as a feature surface that covers app needs, and that all use cases can be address with enough work (regardless of this amount of work)
- the tremendous gap of customizable input api, that would allows easier visual and behavior customization, while enforcing third party expectations support (assistive tech should be able handle it same way as «builtin» input)
- the insistance that CSS flaws (global declarations) are not a roadblock, that implicit, hidden states (from DOM) that can be guessed through JS event handling is a reliable enough solution.
The lack of initiative to solve those problems either means that care is lacking, or that the API is good enough.
The API will be the death of the web. Google won't solve it, Apple won't solve it.
DO IT. If the API is indeed good enough, prove it building an extension atop of it. Leverage your incredible work of those 10 last years on your engine to build the ultimate development platform. Implement it atop standard to have a backward compatibility. Propose it in a first class citizen form to take the initiative on hybride native app with great replacement of the mess Electron is.
To me you have no choice, the alternative is death of the web. At some point, history will be forgotten, and a proprietary vendor will do that, the flash way.
The world would be grateful, and done properly, you'll take back a big chunk of control on the web standardisation, and have large opportunities for sides monetization.
Make the web great. It's your job, only you have an incentive.
> - the insistance that CSS flaws (global declarations) are not a roadblock, that implicit, hidden states (from DOM) that can be guessed through JS event handling is a reliable enough solution.
There is no such insistence, in fact CSS layers, container queries, CSS variables, and Houdini are just some examples of improvements shipped that apply here.
Web can not be dying because "building an app .... is Sisyph-ian challenge".
Web is dying because you try to create apps, not linked documents.
Web is not for apps.
The web is dying under chrome, with the excuse that iOS has its responsibility in the stale doesn't help either.
It's dying, not because of vendors pushing their favorite flavor, but because it has a terrible, horrible API, that make building an app with tightly controller Ui and Ux atop of it a Sisyph-ian challenge.
It's horrible for 3 key points reasons:
- the insistance that the document oriented API (DOM/HTML) as a feature surface that covers app needs, and that all use cases can be address with enough work (regardless of this amount of work)
- the tremendous gap of customizable input api, that would allows easier visual and behavior customization, while enforcing third party expectations support (assistive tech should be able handle it same way as «builtin» input)
- the insistance that CSS flaws (global declarations) are not a roadblock, that implicit, hidden states (from DOM) that can be guessed through JS event handling is a reliable enough solution.
The lack of initiative to solve those problems either means that care is lacking, or that the API is good enough.
The API will be the death of the web. Google won't solve it, Apple won't solve it.
DO IT. If the API is indeed good enough, prove it building an extension atop of it. Leverage your incredible work of those 10 last years on your engine to build the ultimate development platform. Implement it atop standard to have a backward compatibility. Propose it in a first class citizen form to take the initiative on hybride native app with great replacement of the mess Electron is.
To me you have no choice, the alternative is death of the web. At some point, history will be forgotten, and a proprietary vendor will do that, the flash way.
The world would be grateful, and done properly, you'll take back a big chunk of control on the web standardisation, and have large opportunities for sides monetization.
Make the web great. It's your job, only you have an incentive.