• TherouxSonfeir@lemm.ee
    link
    fedilink
    arrow-up
    16
    arrow-down
    3
    ·
    9 months ago

    There are a lot of standard practices like… using a router to load the content of your SPA according to the url.

    • grue@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      9
      ·
      edit-2
      9 months ago

      What I’m saying is, there’s no right way to build a thing that is inherently wrong.

        • grue@lemmy.world
          link
          fedilink
          English
          arrow-up
          7
          arrow-down
          11
          ·
          9 months ago

          Even a perfectly-built SPA is a thing that should’ve been a different kind of program (a native app or even something like Java Web Start) instead.

          • TherouxSonfeir@lemm.ee
            link
            fedilink
            arrow-up
            16
            arrow-down
            1
            ·
            9 months ago

            I strongly disagree, but I respect your opinion which was no doubt formed by different experiences with web technologies than I’ve had.

            • intensely_human@lemm.ee
              link
              fedilink
              arrow-up
              1
              ·
              9 months ago

              Not that it’s inherently good or bad, but the heavier web apps get the more a browser represents a sort of virtualization environment that only runs one stack. I think that’s interesting.

              • TherouxSonfeir@lemm.ee
                link
                fedilink
                arrow-up
                1
                ·
                9 months ago

                What do you mean only runs one stack? Like front end framework? That would be the point. But it can communicate with any backend.