Skip to content
Mr.Kapowski
Mr.Kapowski
  • Home
  • Archive
  • Links
  • Now
  • Projects
    • IndieWeb iOS Shortcuts
    • Saorsa
reply
Chris M.
| June 13th, 2019

💬 Replied to: Introducing the new HTML element - welcome !

“Hello! It looks like you’re writing a blog post – would you like help with that? chuckles Me and my colleagues at Microsoft have decided that the world needs more Clippy – the ado…”

@edent (Terence Eden’s Blog)

The thing for me, putting aside whether the <toast> element is a worthwhile addition or not, is this _feels_ like the plays Microsoft used to make in the Internet Explorer 4/5/6 days. I remember working on the web in that time, and it was *horrible*. I don’t wan’t to go back to anything like it was in those days, where dominant marketshare led companies to think they knew best and could do whatever they wanted with the standards.

The thinking then was the same as now – “we think this is useful, and if other browsers want to the web to remain interoperable, like they say they do, then it’s on them to implement this whether they agree with us or not”. No prior discussion and coming to a consensus with all stakeholders like how the web is supposed to work… just “we have the most users, so we’re doing this regardless.”

Chris M.
est. 1983. He/Him/His. PGP: 8E57C48194665159
Subscribe to author feed
Categories
  • notes
Tags
  • chrome
  • development
  • Google
  • standards
  • web
  • web standards
Syndication Links
  • Home
  • Archive
  • Links
  • Now
  • Projects
    • IndieWeb iOS Shortcuts
    • Saorsa

Chris M.

    • githubGitHub icon
    • twitterTwitter icon
    • microblogMicro.blog icon
    • flickrFlickr icon
    • mastodon.xyzMastodon icon

    est. 1983. He/Him/His. PGP: 8E57C48194665159

    Indieweb Examples

    • IndieWeb Textpattern

    ⬅ An IndieWeb Webring 🕸💍 ➡

    ⬅ Hotline Webring ➡

    This site is powered by HTML and styled with the Autonomie theme