overflowhidden’s avataroverflowhidden’s Twitter Archive—№ 2,398

            1. If I had a blog, I would write a long blog post about this article, but now it's only going to be a few tweets instead. The blog post in question: dev.to/srmagura/why-were-breaking-up-wiht-css-in-js-4g9b
              OpenGraph image for dev.to/srmagura/why-were-breaking-up-wiht-css-in-js-4g9b
          1. …in reply to @overflowhidden
            First of all, I love it when people are honest about their "mistakes", especially when they have invested a lot of time and energy in them, and then share them with the rest of us. So thank you for sharing and going into such detail.
        1. …in reply to @overflowhidden
          Secondly, as someone who has been writing HTML/CSS/JS for more than 20 years, it's obvious to me what has been proven over and over again: bet on the core foundations of the web, and don't try to one-up them. Extend them (think PostCSS etc.) and get the most out of them, but ..
      1. …in reply to @overflowhidden
        .. use them as intended. The people/groups who created and wrote the standards seem to actually know what they were doing. But! Please keep pushing the boundaries, it's definitely needed and appreciated, and will only help us in the long run.
    1. …in reply to @overflowhidden
      Another note: please listen to some of the experienced people who have been along for most of this journey. I dare you to find many of those people, who agreed that CSS-in-JS was a good idea in the first place. Yes, it solved a problem, but it solved it in a bad way.
  1. …in reply to @overflowhidden
    That's it. Thanks for coming to my TED Talk. Now, I'm off to write some HTML/CSS/JS, which I still love doing after all these years.