💾 Archived View for station.martinrue.com › ivanodin › 17477d63402141e598099cd3f394ff20 captured on 2024-06-16 at 12:45:04. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Btw, HTMX for frontend is *chef kiss*
1 week ago · 👍 chirale, falschdenker
@ivanodin depends... on a cms side of things it doesn't really matter and a single page application is a really big deal to write from scratch (multiwindow stuff, forms, icons,...). on the customer side (webshop, content pages, user generated content/login) pure js works quite well. · 2 days ago
@devyl I do agree with you. Vanilla JS is the way to go IMHO. But, in a CoRpoRAte EnViroMenT that's impossible. · 1 week ago
@ivanodin but it's no solution to implement such (indeed really nice) concepts in javascript. it's a waste of cpu cycles "every time" running it with the benefit of a nicer coding experience "once". so one should use JavaScript bare metal as possible imho - i know not every is capable to write performant code via vanillajs... but at least it is possible to waste less cpu cycles x) · 1 week ago
@devyl The ideal world. But my fear is Google trying to then enforce their stupid practices on it. A browser update and boom, the element XYZ now works totally differently. · 1 week ago
... and another bloady javascript library. this would be really great as w3c standard right build into the html spec. · 1 week ago
This is the most fascinating part for me:
https://youtu.be/3GObi93tjZI?t=1204
never tried it though · 1 week ago