On Fri, Apr 1, 2022 at 4:20 PM Anupam Snigdha <[email protected]> wrote:
> Perhaps develop an AI that auto generates bug free code? > > On Fri, Apr 1, 2022 at 1:06 PM Chris Harrelson <[email protected]> > wrote: > >> The API owners did not meet and did not discuss this intent, but LGTM123 >> anyway. >> >> I agree that this intent, seeing as it has no bugs or possible compat >> issues, can skip signals, an TAG review and a more full explainer. >> >> However, I do have a concern for the job security of the engineering >> profession. What will we do instead? I'd appreciate your response to that >> question before shipping, kthxbai. >> > I'm not sure, but I believe the Priority of Constituencies <https://w3ctag.github.io/design-principles/#priority-of-constituencies> means that this issue should not block shipping. On Fri, Apr 1, 2022 at 12:40 PM Jeremy Roman <[email protected]> wrote: >> >>> *Contact emails* >>> [email protected] >>> >>> *Explainer* >>> https://www.rfc-editor.org/rfc/rfc9225.html#abstract >>> >>> *Spec* >>> https://www.rfc-editor.org/rfc/rfc9225.html >>> >>> *Summary* >>> Software defects have been identified as a major pain point for web >>> developers. Accordingly, RFC 9225 deprecates them entirely. >>> >>> *Is this feature supported on all six Blink platforms (Windows, Mac, >>> Linux, Chrome OS, Android, and Android WebView)?* >>> All except Android WebView. Since existing Android apps may rely on >>> bugs, this will require an API level update coordinated with the framework >>> team to ship on Android WebView. >>> >>> *Debuggability* >>> Since RFC 9225 requires that authors not implement bugs, debugging will >>> not be necessary. >>> >>> *Risks* >>> Interoperability and Compatibility: Since no known browser vendor has >>> previously shipped a bug-free browser, there is substantial >>> interoperability risk. There is however no compatibility risk, since any >>> web author depending on existing bugs would themselves be in violation of >>> RFC 9225. >>> >>> Ergonomics: It will be more ergonomic to target a browser engine with no >>> defects. >>> >>> Activation: There is no known polyfill for this feature, which may limit >>> adoption. >>> >>> *Is this feature fully tested by web-platform-tests?* >>> It is partially covered by the root directory of the WPT repository. >>> >>> *Entry on the feature dashboard* >>> >>> *https://www.chromestatus.com/feature/2022040120220401 >>> <https://en.wikipedia.org/wiki/April_Fools%27_Day>* >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "blink-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACuR13fZ%3DEn3b9onDhxQsCcf1mSUa_eKzxr7tG5b8aSzRS01xg%40mail.gmail.com >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACuR13fZ%3DEn3b9onDhxQsCcf1mSUa_eKzxr7tG5b8aSzRS01xg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_bLRwtmZbsc7P5ND-9oEswa4Mi4_68o3SaNgfhu1JPDg%40mail.gmail.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_bLRwtmZbsc7P5ND-9oEswa4Mi4_68o3SaNgfhu1JPDg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACuR13eRyzDbCu677%2BZpPQatqkOWuiTbBy8agSwivFy5rT-fOg%40mail.gmail.com.
