Earlier quoted context omitted.
> it's actually specifically for server-rendered content and using it for front-end development doesn't actually add much It's for server-rendered content that can be used to build a frontend app. I know because I've done it several times. > I would also have to write custom JS for the functions I would try to invoke with htmx The difference is with invokers you would have to re-implement everything from scratch and…
lol. oh boy! everything from scratch! must reimplement the whole library even though I don't package server responses for injection. glad you're enjoying your framework, friend!
Please just try HTMX
471–480 of 530 posts
Re: Please just try HTMX
#472Earlier quoted context omitted.
I am deeply baffled by this kind of response. Firstly, because this site happily handles the amount of traffic that puts many hobbyist sites that happen to get on its front page into a hug of death; so its developers must have done something right on the backend that is probably above the web programming 101 level. But secondly, because this was precisely my point. One does not need a super popular front-end framewor…
> I am deeply baffled by this kind of response. No you're not. You're just trying to respond with something witty. It's a message board with 1% of the functionality most sites people are building with frameworks. > Firstly, because this site happily handles the amount of traffic that puts many hobbyist sites that happen to get on its front page into a hug of death; Lol are you really implying it's hard to scale a mes…
I am implying that it is beyond the "3 pages from W3Schools", as you put it.
> A. Message. Board.
Yes. A fast, reliable, accessible message board that I and many others thoroughly enjoy. An awesome product.
Again, I have never suggested that its ui is complex. In fact, it's glorious how simple it is. This is the point that those htmx people make: use simple tools for simple UIs; and also, try to make your UIs simple.
Re: Please just try HTMX
#473Earlier quoted context omitted.
> It's A MESSAGE BOARD. A. MESSAGE. BOARD. Have you seen how many blog or portfolio sites people build with react? Sometimes even adding nextjs into the mix? Blogs!
So? That doesn't change the fact that HN is a dirt simple message board anybody could build.
What is this an objection to? If you follow this thread upwards, where was it suggested that we should be talking about things so complex that nobody, or only very few, could build? The whole pitch of htmx is that it is proposed for building things that anybody could build. The article in the title assumes that the target audience isn't building Google Docs, Figma, video editors, or CAD tools.
Re: Please just try HTMX
#474Re: Please just try HTMX
#475Earlier quoted context omitted.
> One language has 2 jobs, and the other language 13k jobs. I doubt you'd think for more than a second. The Hacker News website runs on Lisp. How many jobs do you see on the market that ask for Lisp? And yet, for what it is, this site is amazing! I don't see them rushing to migrate to a python backend and a react-based frontend, no matter how many jobs there are for those.
This is all true. But then, if you ran HN and needed to hire new devs, you could find them extremely easily just by posting on your own site. HN is a well-known project that people would want to work on because it looks great on their resume and gives kudos when talking to other devs. In other words, HN does not have the problem that you are going to have if you use an unpopular language for your project. If you choo…
Re: Please just try HTMX
#476Re: Please just try HTMX
#477Earlier quoted context omitted.
I can tell you, it is neither styled, nor does it work on Firefox (as in, properly works). And the mobile UX is horrible.
Perhaps Firefox should focus on shipping a good native datepicker instead of trying to put AI in the browser.
Re: Please just try HTMX
#478Earlier quoted context omitted.
Here's a real-time-ish planning poker written in Go + Htmx in ~500 LoC App (can take a few seconds to spin up if dormant): https://estimate.work/ Source: https://github.com/weiliddat/estimate-work
I mean I built a pretty featureful P2P planning poker app using React and it's around 1300 lines of typescript. More, but I don't think it's a mind-blowing difference and I wasn't playing code golf when I wrote it. I wouldn't have used redux if I was! https://github.com/ceuk/planning-poker
Did a quick test, since before this I also used some very ad-heavy p2p solution, and I see similar issues there. Not sure if you're looking for feedback, but these were all issues I considered before settling on a server-based HTMX long-interrupted-polling approach, which if you think about having server + client + realtime-ish features in the context of "just htmx" + tiny LoC is pretty cool (well I think it's pretty cool :D)
In the WebRTC p2p approach, without some sort of sync protocol that validates the state of data:
- the host must be online / already there to join a room; the host leaving the room means everyone gets kicked!
- if you rejoin a room and don't receive updates, you get a partial view of the data
- if you have data connectivity issues, you get a partial view of the data
- you must have a WebRTC capable browser and Internet connection
Re: Please just try HTMX
#479Earlier quoted context omitted.
lol JSX isn't a language. There aren't "JSX" jobs. I feel like only a backend developer trying to score "gotcha" points could make this argument and be confident about it.
> backend developer You mean a real developer?
Re: Please just try HTMX
#480Earlier quoted context omitted.
> No Jobs > Another practical reason not to use htmx is that there are, rounding off, zero htmx jobs. > I just did a search for htmx jobs on indeed and found a grand total of two: one at Microsoft and one at Oak Ridge National Laboratory. > A search for “react”, on the other hand, gives 13,758 jobs. > Seriously, developer, which of these two technologies do you want to hitch your career to? I do not advocated for htm…
I think the number of job postings is pretty related to factors that I do consider valid when selecting a piece of technology (eg: language, framework, etc): - How easy is it to hire people with experience in this? - Relatedly, how easy will it be for the org to maintain this software after I (or the original team) leaves?