55 karma · joined January 15, 2026
Loading performance on the s website is quite good, and it appears to be using the JS library described in the blog post. I also saw that pages were loading around 60kb or JavaScript or less.
Also, from looking at the author's GitHub profile, it appears that they do not make significant use of LLMs and actually took the effort to write the code by themselves.
I think React is overused, and I'm happy to see people support alternatives.
There is too much ambiguity in English that makes it a poor choice for giving a computer instructions.
LLM AI tech is a scam.
I develop open source software, and I am very specific on what it is able to do. The software doesn't connect to any external dependencies expect for specific services used for authentication and data persistence.
I'm not interested in paying bandwidth costs for bots that don't care about what I posted.
I strongly agree with the approach of making programming more accessible with a simple, deterministic feature set.
It is designed to have a minimal learning curve, and has faster performance than React due to the use of web components.
I don't currently use use HTMX. However, that doesn't invalidate the use of htmx by others when it is a better fit for their experience and use cases.
Using a tool such as htmx is an effective way for them to solve current challenges while minimizing complexity.
Places.js supports component based rendering, and state management integrated with backend data fetching. It also has faster rendering performance than React due to the use of vanilla JS web components.
Places.js is also designed to dynamically render parts of a page while making sure the rest of it is statically rendered. HTMX can be used on those parts, and be used to enhance HTML generated by components through the htmx.process() method. https://htmx.org/api/#process
Writing vanilla JS to manage state and backend data loading can be done with a script that is less than 2kB zipped. The script can then be reused.
I think the design of HTMX acts as a complexity limiter by encouraging less JS. One can make the argument that manually writing JS instead of HTMX would be easier and more maintainable. However, I've found that JS code often trends towards becoming increasingly complex over time.
Also, I'm glad to see that htmx can be installed without npm. I think the ability to install npm packages can incentivize too many dependencies.
However, Postgres is a tool with clearly defined functionality and doesn't have ambiguous requirements that are seen in user facing software. As a result, it is entirely plausible that the author created a working Postgres replacement for certain use cases.
I personally want to see more evidence about the quality of the tool after it is in a finished state.
I'm still skeptical about LLMs and don't use them, although I can be convinced by more demonstrated examples of success.