3 ms·

I don't think the "graphical design" aspect should be the only factor to consider (at least for the general trend, not for wikia in particular). SPA issues shou

by bsaul 9y ago

I don't think the "graphical design" aspect should be the only factor to consider (at least for the general trend, not for wikia in particular). SPA issues should be balanced with the horror that server-side session data is. Trying to rebuild the client-side state every time after each answer. From a programming model POV, having the server only spit the necessary data for the new info required, and not the whole set together with GUI data, is a real simplification. Not to mention the fact that it is already the architecture you need for the other types of client (mobile and native desktop app).

cabalamat 9y ago
> the horror that server-side session data is Whast is horrible about this?
- bsaul 9y ago
  Well, for once it means resending over and over the same information on every page, it's just a waste of bandwidth. Then it makes sharding the server more complicated, because you need to make sure the request goes to the correct server (or you have to use a special DB just for that such as redis). For things as simple as form validation, you need to resend the values that the person entered in case the form didn't validate. Then you end up piggybacking informations from one page to another in hidden type form fields... If that doesn't sound crazy to you, then you should probably write "native" application again, it will remind you how simple life is when your client has the right to use its memory.
hellofunk 9y ago
I don't quite understand the relevance here of the server. An SPA may or may not have a tight interaction with a server. Most of the time, an SPA to me is mostly living as a browser process, with occasional interaction with a server, but that doesn't have to be the case. If it is too tightly tied to a server, then it's not really a true front-end application, it's more like a web site in that regard. SPAs are usually more than a window into a server, they are a dynamic application unto themselves.

by bsaul 9y ago

cabalamat 9y ago

> the horror that server-side session data is Whast is horrible about this?

bsaul 9y ago
Well, for once it means resending over and over the same information on every page, it's just a waste of bandwidth. Then it makes sharding the server more complicated, because you need to make sure the request goes to the correct server (or you have to use a special DB just for that such as redis). For things as simple as form validation, you need to resend the values that the person entered in case the form didn't validate. Then you end up piggybacking informations from one page to another in hidden type form fields... If that doesn't sound crazy to you, then you should probably write "native" application again, it will remind you how simple life is when your client has the right to use its memory.

hellofunk 9y ago

I don't quite understand the relevance here of the server. An SPA may or may not have a tight interaction with a server. Most of the time, an SPA to me is mostly living as a browser process, with occasional interaction with a server, but that doesn't have to be the case. If it is too tightly tied to a server, then it's not really a true front-end application, it's more like a web site in that regard. SPAs are usually more than a window into a server, they are a dynamic application unto themselves.