3 ms·
This is perhaps the oddest point the article makes. They argue that JavaScript is still available for its “originally intended” purpose of light scripting, but
by kiawe_fire 5y ago
This is perhaps the oddest point the article makes.
They argue that JavaScript is still available for its “originally intended” purpose of light scripting, but that using less JS on the front end somehow frees you to use whatever you want on the back end.
But there is nothing inherent to SPAs that would force anyone to use JS on the back end.
And if “diversity is our strength” then I see no reason that wouldn’t be equally true when building JS-heavy SPAs.
- naasking 5y agoYou're maintaining two development environments without also using JS on the backend, and require developers that are skilled with both environments and languages. This isn't really an issue with htmx, or with using JS at both ends.