• Lemminary@lemmy.world
    link
    fedilink
    arrow-up
    12
    arrow-down
    10
    ·
    edit-2
    3 months ago

    Can we not do away with CSS/JS, learn from those mistakes and try something else? Pls, I beg you 🥺🙏

    E: Sorry, forgot the /j Lighten up, Lemmy, not everything is a serious comment that needs your scrutiny or meticulous rebuttals.

    • yogsototh@programming.dev
      link
      fedilink
      arrow-up
      6
      ·
      3 months ago

      The first pass of elm ecosystem solved it. Before elm, it was also solved by other frameworks. But people wanted to be able to reuse their components and not rebuild new ones. React provided the ability to reuse css, and dirty js code in the middle of your application. You already had an way bigger ecosystem because you didn’t have to learn and built a complete new system again.

      Personally if I had the choice I believe a new start should start at the browser level. Stop supporting HTML/CSS/JS. Create a new app-centric DSL and not a document centric one like html/css/js.

      Ideally something inspired from cocoa layout. And I am dreaming but not accept generic code on the client side and only support a small controlled API. It would solve so many security issues. Sure, the creativity in such an ecosystem will be severely reduced. But we will have a so much improved UX.

      • pixel_prophet@lemm.ee
        link
        fedilink
        arrow-up
        6
        arrow-down
        1
        ·
        3 months ago

        I get the reasoning but anything like that would just be abused to enshittify things further with unblockable ads and enforced DRM on everything. At least with the open standards there is the ability to adblock and manipulate certain annoyances at a browser level

    • Olap@lemmy.world
      link
      fedilink
      arrow-up
      9
      arrow-down
      1
      ·
      3 months ago

      What would you replace it with? There are lessons to be learnt from the web, but to “fix” it is much harder