• ______@lemm.ee
    link
    fedilink
    arrow-up
    11
    arrow-down
    1
    ·
    1 year ago

    I learned about how much I didn’t understand react on my 2nd dev job. I had like 2yoe with react previously. There’s a lot about it. Mostly tricks. hacks and work arounds for it’s abysmal performance.

      • ______@lemm.ee
        link
        fedilink
        arrow-up
        8
        ·
        1 year ago

        There many ways of doing things in react and some are faster than others. I would abuse state and use effect at my old job but at this job my sr dev doesn’t allow me to use useffect unless the situation warrants it.

        • tsonfeir@lemm.eeOP
          link
          fedilink
          arrow-up
          3
          ·
          1 year ago

          Ahh yes, abusing state can be temping. Just a little tweak here, it’s ok… no one is looking… oh crap!

          • TitanLaGrange@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            edit-2
            1 year ago

            I’m relatively new to React (about 8 months in with React Native). Can you give me some examples of abusing state?

            At one point I was struggling with getting an edit control to render when I wanted (an issue with controlled vs non controlled) and I found myself setting a do-nothing state to force a rerender. That fixed my immediate issue, but I knew it was wrong enough that I had to come back to it later and revise the whole screen (went and learned how to use reducers which made everything on my more complex screens easier).

    • Potatos_are_not_friends@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      I’m not at all a React fan, and prefer vanilla or Vue.

      But what is happening where you’re hitting abysmal performance?

      Are you blaming the implementation or the tools because while I can achieve faster performance with vanilla… In no way is abysmal a word I’d used.