This covers a topic I'm passionate about, but I mean… Sorry if that sounds dismissive, but if you want to build a frontend that lasts for decades, the correct way to do that is to use vanilla-js: that's the only way to protect yourself from breaking changes, unmaintained dependencies and dependency hell . We've got so used to adding javascript libraries that nobody even considers whether vanilla html/js/css would be enough - despite all the cool things that happened in there (webcomponents, html templates, shadow DOM, etc). I even see people still using SCSS just to have rules nesting and variables, not even realizing it's now natively supported. I applaud the fact that you're trying to get your ideas into web standards, that's the way to go. But well, see you then. :)
Amazing talk, he has a great way to articulate his points.
So, Go for the backend, SqLite for Db & HTML, CSS, JS for frontend ??
👋Great talk! 👏
Amazing talk.
This covers a topic I'm passionate about, but I mean… Sorry if that sounds dismissive, but if you want to build a frontend that lasts for decades, the correct way to do that is to use vanilla-js: that's the only way to protect yourself from breaking changes, unmaintained dependencies and dependency hell . We've got so used to adding javascript libraries that nobody even considers whether vanilla html/js/css would be enough - despite all the cool things that happened in there (webcomponents, html templates, shadow DOM, etc). I even see people still using SCSS just to have rules nesting and variables, not even realizing it's now natively supported. I applaud the fact that you're trying to get your ideas into web standards, that's the way to go. But well, see you then. :)
I guess you know that you can (and should) host HTMX on your server, and it's written in vanilla JS.
12:00 Sqlite!