5 ms·
HTML, plain CSS, vanilla JavaScript to fetch data / interactivity when required. mod_perl / PostgreSQL on the back end. HTML::Mason for templates.
by hestefisk 4y ago
HTML, plain CSS, vanilla JavaScript to fetch data / interactivity when required.
mod_perl / PostgreSQL on the back end. HTML::Mason for templates.
- doctor_eval 4y agoIMO, the problem with vanilla JS on anything other than trivial pages is you end up having to implement a bunch of common patterns (such as interpolation and form binding) and before long you’ve got what is effectively a private framework that you’ve kludged together in an ad hoc way while simultaneously trying not to be distracted from solving your actual problem. But because it’s come about in this organic, unfocussed way, it will have a bunch of bugs and caveats, and it will be a bit of a mess. And don’t even get me started on browser engine differences. Better to pick one of the lightweight frameworks (like Vue, which is super simple to integrate into plain html/css), and save yourself some pain.
- hestefisk 4y agoI prefer my own mess over someone else’s mess :)
- doctor_eval 4y agoI do fully agree with this normally! But Vue and a few others are so lightweight and well tested that I feel like I’m being crazy if I reimplement them. Of course YMMV, I do a lot more backend than frontend.