←back to thread

858 points colesantiago | 1 comments | | HN request time: 0s | source
Show context
bergfest ◴[] No.45109168[source]
They should be barred from shipping experimental or non-standardized features in Chrome to prevent them from abusing their monopoly and forcing others hands by creating de-facto standards without a fair discourse. Experimental features should be allowed in special Chrome builds targeted at developers only, and not be allowed to come preinstalled on any consumer device.
replies(2): >>45109191 #>>45109309 #
skybrian ◴[] No.45109309[source]
Why? It seems like new API's should be tested with real users before becoming a web standard, and origin trials were a big improvement over what happened before with webkit specific CSS, etc.
replies(2): >>45109545 #>>45111238 #
1. maxloh ◴[] No.45111238[source]
This is actually the case for ECMAScript (JavaScript).

All proposals must first be implemented by some browser vendors at Stage 3:

> The proposal has been recommended for implementation.

Then, the proposal shall be included in the standard at Stage 4:

> Two compatible implementations which pass the Test262 acceptance tests

https://tc39.es/process-document/