rockerest’s avatarrockerest’s Twitter Archive—№ 18,902

      1. …in reply to @claviska
        claviska Wild that someone implemented a V0 tool that was only ever shipped in one browser and was pained to find that they needed to rewrite it when the spec finally landed in all the browsers 2-3 years later.
        Permalink On twitter.com Twitter logo rockerest’s avatar ❤️ 1 Favorite 2022 Feb 14 Mood -2 🙁
    1. …in reply to @rockerest
      claviska And has since rewritten in a library that's not standardized anywhere, using fundamental things like JavaScript and HTML. Should we tell them those things are the future proof part of the framework?
      Permalink On twitter.com Twitter logo rockerest’s avatar ❤️ 1 Favorite 2022 Feb 14 Mood +2 🙂
  1. …in reply to @rockerest
    claviska I'm a huge Web Components booster, but I didn't get involved until things started shipping as part of specs (V1) because [checks notes] uh [double checks] I wanted to natively support all the browsers and I don't want to have to rewrite it later...
    On twitter.com Twitter logo rockerest’s avatar ❤️ 2 Favorites 2022 Feb 14 Mood +2 🙂