4 ms·

> A JSON containing the data to update a piece in the page will always be measurably smaller than the full UI There's no need to compress the full UI again. Ra

by jhgb 4y ago

> A JSON containing the data to update a piece in the page will always be measurably smaller than the full UI There's no need to compress the full UI again. Rails' Turbo for example transfers only the minimum fragment required. > Sure you can make outputs for multiple clients just as easily. On the traditional SPA though, you don't need to make those at all. Neither do you have to do that in a traditional MPA. One client = one frontend, surely? > You literally called it "hiring difficulties". What's the point to argue after this? Did I misunderstand the comment I was responding? You wrote "people have limited time and energy to specialise". The way I interpreted it was that different people have different strengths, so it's difficult to hire someone who has many different strengths at once (and for example wouldn't poke a hole in your PHP code, to use your own example).

mrtksn 4y ago
> here's no need to compress the full UI. Rails' Turbo for example transfers only the minimum fragment required. That's SPA fetching HTML instead of JSON or something. You are welcome.
- jhgb 4y ago
  As per Wikipedia: > In a SPA, a page refresh never occurs This is not true with something like Turbo: the partial transfer may or may not take place depending on whether it's useful to do that. The point is that you don't have to even care about that (and I'm not even sure you even any control over that). From the perspective of a Rails programmer, you're generating whole pages. How they get to the client is immaterial to you. Think of it as compression (which is actually is, basically using the previously tranferred data as a dictionary).
  - mrtksn 4y ago
    It's alright, Rails programmers can do that. Nice little trick for building SPAs. There are other systems that use the technique, it has some advantages and disadvantages. If it works for you, great. What's the point to argue against the advantages of SPA?

by jhgb 4y ago

mrtksn 4y ago

> here's no need to compress the full UI. Rails' Turbo for example transfers only the minimum fragment required. That's SPA fetching HTML instead of JSON or something. You are welcome.

jhgb 4y ago
As per Wikipedia: > In a SPA, a page refresh never occurs This is not true with something like Turbo: the partial transfer may or may not take place depending on whether it's useful to do that. The point is that you don't have to even care about that (and I'm not even sure you even any control over that). From the perspective of a Rails programmer, you're generating whole pages. How they get to the client is immaterial to you. Think of it as compression (which is actually is, basically using the previously tranferred data as a dictionary).
- mrtksn 4y ago
  It's alright, Rails programmers can do that. Nice little trick for building SPAs. There are other systems that use the technique, it has some advantages and disadvantages. If it works for you, great. What's the point to argue against the advantages of SPA?