• flashgnash@lemm.ee
    link
    fedilink
    arrow-up
    42
    ·
    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

      • xthexder@l.sw0.com
        link
        fedilink
        arrow-up
        11
        ·
        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
          4
          ·
          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
            3
            ·
            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.

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

              Yes I mean react native

              Wouldn’t be bothering with it if I were just working with web

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

                Using capacitor as a native shell for your web app can be very nice, actually. It lets you hook into native API calls and build native apps while hardly ever having to write native code, unless you want to, which presumably you don’t since you’re writing react native.

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

                  Honestly doing it again I’d just write in xamarin or something not web orientated because as it turns out the web app is going to need to be separate anyway

                  I might look into capacitor but is that not basically just electron?

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

                    I guess you could see it that way, but web views are inherent in mobile operating systems, they don’t need to be bundled into your app, so capacitor apps aren’t big bloated memory consuming applications like electron apps are. There’s a lot of well made apps running on capacitor that you wouldn’t even know, especially if you use something like ionic framework to actually have the look and feel of native mobile apps.

        • bitfucker@programming.dev
          link
          fedilink
          arrow-up
          4
          ·
          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

          • uis@lemm.ee
            link
            fedilink
            arrow-up
            3
            ·
            edit-2
            7 months ago

            No framework will make FSM for you. Managing state of web ui is not as hard as managing state of game.

            Using TCP for networking? Loss, retransmit, lag, you’re dead. Using UDP for networking? Loss, desync, you’re dead. Sending full game state? Congestion, loss, lag, dead. Doing sync right, but still pushing too much data? Congestion, loss, lag, dead. Also keeping on server you need not only track game state, but what game state client confirmed to receive.

        • traches@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          2
          ·
          7 months ago

          The biggest problem frameworks solve is “I need the value of this variable to be on the page and I need it to stay up-to-date.” If you don’t have this problem, or you only have it in a couple of places where hand-writing the necessary event listeners isn’t too arduous, then yeah you don’t really need a front end js framework.

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

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

      • flashgnash@lemm.ee
        link
        fedilink
        arrow-up
        5
        ·
        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”

        • uis@lemm.ee
          link
          fedilink
          arrow-up
          3
          ·
          edit-2
          7 months ago

          and in rust’s case sometimes even how to fix it

          Then there’s C with “segmentation fault”

          1. You are comparing compiler-generated errors and runtime errors
          2. Rust can trigger segmentation fault and bus error too.
          3. GCC’s error messages are very detailed, sometimes can contain suggested solutions.

          For example if I will try to compile helloworld without including stdio.h, gcc will warn implicit declaration of functionprintf(by default, almost everyone make it error with -Werror=) and will suggest note: include ‘<stdio.h>’ or provide a declaration of ‘printf. And runtime error reports are as good as programmer makes them, no matter language program was written in.

          I am spoiled by core dumps(although rust technically has them too).

          Also in context of kernel, it will print stack trace and (if used) will kexec into another kernel that can make core dump or continue working.

    • sandman@lemmy.ca
      link
      fedilink
      arrow-up
      2
      ·
      7 months ago

      I just have to say: designing a GUI in code in 2024 is asinine.

      I feel bad for anyone who got suckered into learning convoluted bullshit like angular or react when they could’ve learned Godot or Qt.