Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web semantics #280

Closed
gedw99 opened this issue Aug 29, 2023 · 1 comment
Closed

Web semantics #280

gedw99 opened this issue Aug 29, 2023 · 1 comment

Comments

@gedw99
Copy link

gedw99 commented Aug 29, 2023

Cool architecture @erichanson

it’s data all the way down :)

checkout htmx. It’s a good match to the way your web semantics works.

htmx is old school with a simple way to describe interactions whereby the web page is progressively changes using a very simple data notation.

the concepts are rooted in how your whole architect works in that your capturing the delta / diff.

There’s pls try of golang htmx examples out there and you can use SSS or WSS are your transport with zero code changes .

@erichanson
Copy link
Member

Thanks for the feedback!

I checked out htmx, spent some time with it. I could see how some folks would like it, but to me it feels like the product of the constraints that the file-based paradigm imposes on coders. You don't want to have an HTML file, CSS file and JS file for each component of each page, because, files. Aquameta very much embraces separation of concerns at the web level (and ideally everywhere else) so conflating them all together in one file feels like a step backwards. My two cents. Interesting stuff though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants