Re:A single-page app is almost always worse than a multi-pag...
by paulie_a on Tuesday October 30, 2018 @10:32AM
(#18336803)
Honestly no it wouldn't suck and from a end user perspective for a calendar. It is actually far superior. Granted this is only my personal opinion. There seems to be this desire to overcomplicate the front end when simple solutions work quite well. Granted they don't have all the catchy buzzwords. But they make for a better less bug filled solution.
[ Parent
| on HN ]
Re:A single-page app is almost always worse than a multi-pag...
by bauerd on Tuesday October 30, 2018 @10:38AM
(#18336870)
Calendar UIs commonly demand stuff like auto-refreshing, datetime selects, drag-dropping items around, resizing those, list goes on. Please elaborate how you'd build a "simple solution" that does not resort to client-side rendering.
Re:A single-page app is almost always worse than a multi-pag...
by wild_preference on Tuesday October 30, 2018 @12:15PM
(#18338191)
Yeah, even a "Select All" button that checks all checkboxes requires Javascript.
Aside: I don't understand the premise of this thread that suggests it's a "SPA" just to, say, use React on a single page of an application. The whole basis of the "SP" in "SPA" is that the Javascript (state) spans multiple pages.
Re:A single-page app is almost always worse than a multi-pag...
by PurpleBoxDragon on Tuesday October 30, 2018 @12:26PM
(#18338351)
I once worked with a guy who built an app with everything done server side in web forms, including a datetime picker. It stands out in my memory as one of the worst pieces of software I've ever seen produced.
Re:A single-page app is almost always worse than a multi-pag...
by TopWaltz on Tuesday October 30, 2018 @01:29PM
(#18339148)
> I once worked with a guy who built an app with everything done server side in web forms, including a datetime picker
ASP.NET Webforms? I have good memories of being able to do that easily, with zero (or almost zero) JavaScript.
It's not the best user experience ever (the whole page has to reload after each click, and the state is persisted by serializing structs in <input type="hidden"> fields), but I had a pleasant experience when I developed with it.
ASP.NET Webforms components were the best thing until we finally had React/Vue!
The only problem was that it was way too easy to make a mess in your backend code.