re: Todo-MVP: Or 'Why You Shouldn't Use A Web Framework' - The Revenge VIEW POST

re: Because I was using 90xx web. Page refresh doesn't happen fast enough as background interactions and rendering result as it arrives. This implies ...

You can definitely (and should totally) not bundle and serve megs of Javascripts with each page but cherry pick for each necessity; and we also did invent SSR so you can for sure not show a white page on first load. You can do animations with CSS and handle DOM changes with a library like Preact which is like a handful of kilobytes, and still use plenty of vanilla JavaScript so you keep it fast and lean; even adopt stuff like Tachyons or FontAwesome if you want to ship something professional looking. All of this doesn't require megs and megs, just common sense and some tools made by awesome people you can find around.

Sure you could do it backwards and do it the good old fashioned way of "I click, it reloads", but then when the server will be slow or even go 504 users will complain it's slow and unreliable, while you could've used AJAX (which we've been doing for a looooong while now) and provided helpful, human readable status messages without sending your users out or even losing their work because your API aren't reliable.

You can also do both, use server side templating and use JS to augment the website and cache.

Basically what is doing and being pretty fast at it too.

There's no single way to build a website anymore and that's great for everyone, yeah the complexity of frontend programming is escalating, but there is a lot of innovation going on at the same time

code of conduct - report abuse