• grue@lemmy.worldEnglish
    1014·
    11 months ago

    > implying there’s a “right way” to build an SPA.

    • tsonfeir@lemm.ee
      163·
      11 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.worldEnglish
        89·
        11 months ago

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

        • tsonfeir@lemm.ee
          71·
          11 months ago

          You could build it with no input sanitation. That’s wrong.

          • grue@lemmy.worldEnglish
            711·
            11 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.

            • tsonfeir@lemm.ee
              161·
              11 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
                1·
                11 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.

                • tsonfeir@lemm.ee
                  1·
                  11 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.

    • andrew@lemmy.stuart.funEnglish
      4·
      11 months ago

      There’s no one right way. Saying there are wrong ways doesn’t imply the existence of one right way, though.