> But you can write React in this library-like manner too and nobody argues that React isn’t a framework.
I think people do still make this argument
Is htmx Just Another JavaScript Framework?
11–20 of 318 posts
Re: Is htmx Just Another JavaScript Framework?
#12So what's the problem with a bundler/transpiler etc?
You set it up once. It takes a few hours, maybe a day. Then your platform _is_ TypeScript + React. This abstraction basically never leaks. I never need to look at the transpiled files to find an error.
Nobody argues that a C compiler is worse than assembly or that drivers or an operating system are bad.
Re: Is htmx Just Another JavaScript Framework?
#13I like this article, it's interesting.
I will say that in the web dev world I'm a whole lot less worried about definitions than I am trying to figure out what library or framework works for given use cases, what its benefits are ... and where it stops being helpful.
That's not information that is nearly as easy to write though and sadly seems to just take trial and error by each individual.
Re: Is htmx Just Another JavaScript Framework?
#14I prefer to refer to htmx as a "future polyfill". Eventually, htmx semantics will become part of the web standard, and older browsers (or those that choose not to implement the feature) will need this polyfill.
Re: Is htmx Just Another JavaScript Framework?
#15It is not the same at all. Of course it needs javascript on the back to work. But the concept is totally different. It uses a hypermedia declarative model, an extended POST/GET etc. model. It keeps things very simple compared to a framework like React where you need a package manager, a transpiler and a json backend for data (not returning hypermedia). So I would not consider it another Javascript frontend framework…
that's true, it also need more support from the backend, for react a restful background is all you need, for htmx or html+ajax the backend has to do routing, state management,etc, it's really the traditional MVC approach, but easier for the frontend(no json, just html)
Re: Is htmx Just Another JavaScript Framework?
#16So what's the problem with a bundler/transpiler etc? You set it up once. It takes a few hours, maybe a day. Then your platform _is_ TypeScript + React. This abstraction basically never leaks. I never need to look at the transpiled files to find an error. Nobody argues that a C compiler is worse than assembly or that drivers or an operating system are bad.
Once you're in the NPM ecosystem, there is a maintenance overhead.
See:
Re: Is htmx Just Another JavaScript Framework?
#17Yes
Re: Is htmx Just Another JavaScript Framework?
#18Haven't heard of htmx before, but I might use it on a future project if I remember.
As somebody who is not a frontend engineer, but still likes to make a website every now and then. I haven't found a full framework (vue, react, etc.) that I've been able to go full into and still use jquery and writing plain css/html.
Htmx looks like a slight feature upgrade to jquery that I enjoy.
Re: Is htmx Just Another JavaScript Framework?
#19So what's the problem with a bundler/transpiler etc? You set it up once. It takes a few hours, maybe a day. Then your platform _is_ TypeScript + React. This abstraction basically never leaks. I never need to look at the transpiled files to find an error. Nobody argues that a C compiler is worse than assembly or that drivers or an operating system are bad.
The problem is that it's no longer an "interpreted" language.
Re: Is htmx Just Another JavaScript Framework?
#20Yes
Thank you.