4 ms·
My style for building web app. I was never convinced that doing everything on JS layer is a good thing (regardless the backend language). But you need to show
by didip 2y ago
My style for building web app. I was never convinced that doing everything on JS layer is a good thing (regardless the backend language).
But you need to show more interactivity to convince the JS people.
I personally like this style and add HTMX for partial updates.
- szundi 2y agoDepends on what you want to do
- catlifeonmars 2y agoIt depends strongly on what you’re building. Interactivity is a property of the app and different types of apps have different interactivity requirements. For example a page that is more or less a UI proxy for CRUD operations typically does not require too much client side state. On the otherhand, a flow chart editor (any document editor really) needs to function largely without round trips to the server. If the web app is intended for mobile, you would expect to see many more interactions with limited bandwidth or no internet connectivity, so you would need to account for that. This is much more about application architecture than preference (although you can certainly choose to only work on applications that match your preferences).
- fallinditch 2y agoGood perspective, thanks, this is the kind of information that is often hard to find: deciding on a tech stack is nuanced, is more than preferences. I am looking for a good source of information about approaches to application architectures that is relevant to modern times.
- slmjkdbtl 2y agobut JS is the only answer to client side interactivity without hacks, there's nothing to be convinced