• naught@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    5
    ·
    3 months ago

    When your entire code base is in typescript and you have multiple people working on it, straight HTML feels like stepping backwards in time. Just because it’s possible to do a lot of interactivity without React doesn’t mean it’s simpler or easier for the team

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

        A part of me agrees with you, however, the forced structure of components does tend to remove some of the opportunity for accidentally breaking other people’s functionality. Usually. That said, React is a huge pain in the ass, and often. And keeping npm dependencies up to date is a fuckin hassle. I should know, that’s one of the roles I’ve taken on, and it sucks.

          • TrickDacy@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            arrow-down
            1
            ·
            edit-2
            3 months ago

            I just have an aversion to overengineering things.

            This is me exactly ^

            Currently a team mate is rewriting something I built which was simple and worked, and was just slow. It’s an internal tool, and what we’re doing is expected to be slow. So it annoys me a lot that they are now making it needlessly complex when the way I did it was not ideal in performance but worked. The service is gonna be used like 30 times per week. He’s gonna spend a week and add complexity/maintenance to save $15 a month in cloud computing… I hate it.