• flashgnash@lemm.ee
    link
    fedilink
    arrow-up
    1
    ·
    7 months ago

    Made the mistake of using react for a mobile app and my god why is it this convoluted, why are the error messages always along the lines of “something went wrong with networking 🤷”

    Unfortunately I’m stuck with it now

    • uis@lemm.ee
      link
      fedilink
      arrow-up
      1
      ·
      7 months ago

      Linux has better error messages. “Dazed and confused, but trying to continue”.

      • flashgnash@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        7 months ago

        I am spoiled by dotnet and rust error messages. They tell you exactly what the problem is, where it is, and in rust’s case sometimes even how to fix it

        Then there’s C with “segmentation fault”

      • xthexder@l.sw0.com
        link
        fedilink
        arrow-up
        1
        ·
        7 months ago

        Am I the only one left writing pure JS webpages? I swear for the stuff I’ve done recently, adding React or even jQuery makes things 10x more complicated and bloated. The base JS support browsers have now is actually great. It’s not like the old days trying to support every browser back to IE6

        • flashgnash@lemm.ee
          link
          fedilink
          arrow-up
          1
          ·
          7 months ago

          I like base JS and I like jQuery. Only reason I’m using React is for native cross platform mobile/web but I’m beginning to regret choosing it for that

          • body_by_make@lemmy.dbzer0.com
            link
            fedilink
            arrow-up
            1
            ·
            7 months ago

            I assume you mean react native, not react, unless you’re using something like capacitor. React native is a far shot from react and is much more annoying to deal with.

        • bitfucker@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          7 months ago

          When you are writing some complex web app, you will wish you used a framework. Some web apps can have more than 50 pages with multiple states that depend on remote data to be locally cached and synced depending if you are online/offline. Framework can handle a lot of the heavy state management for you and even provide a nice UI component library. But I do agree that React is too much, but jQuery is being replaced by vanilla JS. That is why I usually use Vue. But for simple stuff, yes, Vanilla JS is pretty much good enough

  • lorty@lemmygrad.ml
    link
    fedilink
    arrow-up
    1
    ·
    7 months ago

    Backend developer: “The new functionality is done!” PO: Looks at tests “Seems good, ship it!”

    Frontend developer: “The new functionality is done!” PO: Looks at his screen “This spacing could be a little to the right, also I think I didn’t really like this text, also it should probably auto-scroll to the top and this button should change colors when I click it and also don’t forget to change the error messages I was happy with before and also I think it should…”

    • xmunk@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      7 months ago

      I remember the day of php files outputting html to the browser… it was 95% as functional as the stuff written in react and node today and incredibly simple.

      Heck, at my company, I still sneak in old-school HTML files when I can.