101–110 of 146 posts
Earlier quoted context omitted.
can you comment on what those 500 lines actually were? react+redux?
It was all normal JS code to handle a complicated form we have on a customer facing portal page. By moving to htmx I was able to rely on the server side to handle basically everything with only a small addition of code to what it was already doing.
Earlier quoted context omitted.
It was all normal JS code to handle a complicated form we have on a customer facing portal page. By moving to htmx I was able to rely on the server side to handle basically everything with only a small addition of code to what it was already doing.
Isn’t that moving code around, not deleting it?
Htmx users, can you please share your backend stacks and approaches? Me specifically interested in templaters for node (+ts) and your thoughts on endpoint management, but all ideas are welcome I guess.
Well, as I expected, templating is the hardest part of migrating to htmx on nodejs. After reviewing few templaters/etc (handlebars, ejs, lit-html, virtual-dom) and few abstractions (html``, just ``, h()), barely anything seems too easy and too freedom-y. Arcane syntaxes, high character noise (ejs, lit, js), lack of typing (all non-`` based), trivial screw ups (virtual-dom, handlebars), experimental status (lit ssr).…
I use PUG. I don’t like to close HTML tags. This cuts 30% of the visual bloat out of my templates.
Earlier quoted context omitted.
can you comment on what those 500 lines actually were? react+redux?
It was all normal JS code to handle a complicated form we have on a customer facing portal page. By moving to htmx I was able to rely on the server side to handle basically everything with only a small addition of code to what it was already doing.
Earlier quoted context omitted.
Well, as I expected, templating is the hardest part of migrating to htmx on nodejs. After reviewing few templaters/etc (handlebars, ejs, lit-html, virtual-dom) and few abstractions (html``, just ``, h()), barely anything seems too easy and too freedom-y. Arcane syntaxes, high character noise (ejs, lit, js), lack of typing (all non-`` based), trivial screw ups (virtual-dom, handlebars), experimental status (lit ssr).…
This was my experience as well. No great template generator on the node side. I use PUG. I don’t like to close HTML tags. This cuts 30% of the visual bloat out of my templates.
One man's structure is another man's "bloat", I guess.
Htmx users, can you please share your backend stacks and approaches? Me specifically interested in templaters for node (+ts) and your thoughts on endpoint management, but all ideas are welcome I guess.
Earlier quoted context omitted.
It was all normal JS code to handle a complicated form we have on a customer facing portal page. By moving to htmx I was able to rely on the server side to handle basically everything with only a small addition of code to what it was already doing.
I'm qurious what that code was doing that could be just moved to the backend. Usually forms have some validation for a better experience with the final validation on the server. Did you get rid of that and just show an error if the submission failed?
Its like old school for validation back in the CodeIgniter days.
Earlier quoted context omitted.
Huge congrats on the major number release. HTMX is simply wonderful. Using it for a major project as we speak!
Would love to hear more about how you’re using it
The entire experience using Go + Fiber (gofiber.io) + templates + HTMX (htmx.org) is fantastic. This approach has allowed us to create a beautiful modern application that's highly performant, interactive in all the places you'd expect, and simple code, deps, devops, etc.
Earlier quoted context omitted.
This was my experience as well. No great template generator on the node side. I use PUG. I don’t like to close HTML tags. This cuts 30% of the visual bloat out of my templates.
removingspacesgotridofalotofmybloatonregulartexttoo. One man's structure is another man's "bloat", I guess.
What it removes is the visual bloat of closing html tags.
So instead of:
Some content
More content
Another paragraph
#foo.bar.baz
p Some content
#foo2.bar2.baz2
p More content
p Another Paragraph
And it's easier to visually parse element IDs and chained classes this way too.