3 ms·
IMO the biggest hurdle in frameworks like Svelte or Next isn't the framework -- it's the language. This type of app is a prime use case for something like Live
by oDot 2y ago
IMO the biggest hurdle in frameworks like Svelte or Next isn't the framework -- it's the language.
This type of app is a prime use case for something like LiveView or a Go framework. Just today I had the most marvelous experience using Tailscale's ACP, where I've changed the ACL and it instantly saved it. It was so fast I had to make sure it's not optimistic UI, and sure enough, 78ms round trip for the request.
Even if it was a FE-heavy app using SQLite in the browser, I wouldn't have used JavaScript. After months of Gleam, I am spoiled.
The days of JavaScript-because-we-have-to are thankfully over. JS is now only for when the flexibility is required.
- seanvelasco 2y agothe reason I use JS is def not flexibility, it's to enhance the usability and interactivity of my app. even for my Python and Go web apps, I still inline JS to achieve the functionality I want. examples: client-side routing, pin the scroll to bottom, mutating classList, etc
- salomonk_mur 2y agoYeah, that ability to improve usability beyond the basics is what he means by flexibility I think. I agree with that sentiment. I can now build decent, working websites in something like Streamlit without touching JS (even if JS is being generated behind the scenes).
- oDot 2y agoGleam compiles to JavaScript, so JS is not needed for that extra frotnend flare. The flexibility to sprinkle some code here in there is definitely unique to JS