re: Some questions about SPA UX VIEW POST


The Laravel community, especially the LaraCasts author Jeffrey Way, is mostly against SPAs and Flux (Elm) like central stores, at least. In the words of Jeffrey from a podcast interview: "Sure, it's cool, but . . . is it useful?"

Yeah, it really is. Speaking for Elm anyway. But you model central stores differently, especially with Elm union types.

I mostly write SPAs nowadays. The client-server separation forces a more-or-less healthy mental model of how the UI should be separated from interaction with back-end resources. I also had particularly bad experiences with server-side components trying to abstract rendering details from me, but then I depend on those rendering details for styling purposes, or the generated scripts interfere with other scripts. So being able to take control over those things if necessary on the client side makes solutions easier to achieve.

jQuery... no I don't do that anymore. Last time I did, I was not pleased how it turned out. MVU (Elm) style is pretty much the only way I would do SPAs anymore until someone comes up with something better. Mainly because most of the code is my own code, not incantations to invoke the framework features "just right".


True. I included Elm because that's where the original idea comes from, although Redux/Flux seems to take all the credit. 😏

I think the higher your skill-level as a front-end dev, the more these things make sense. Juniors absolutely love jQuery, because there are so many elegant plugins out there; mid-level developers like me know the pain of jQuery, and also know that frameworks are better, but their front-end skills hold them back from making a complete switch; really experienced ones are either writing in Elm or even vanilla JS.

All this said, though, consulting (freelancing) is a different beast. They (includes me) need to get the job done in the least possible time, which obviates stuff like React, SASS, unit testing, browser testing, and so on.

code of conduct - report abuse