neeleshs

I use LLM to generate complete solutions to small technical problems. "Write an input stream implementation that skips lines based on a regex".

Hard for an IDE auto complete to do this.

Or a tapestry! (I have one in our dining room)

I see. HTMX and others target the browser, which is primarily an HTML renderer. So there is nothing inherently bad about page transfers. That's what hypermedia is about.

React et al try to create a different paradigm on top of this. And that makes it like building a desktop UI AND a server app

To me, this is not in anyway better than building something for the browser - pages and html.

Can you say more about what didn't work with HTMX? What parts make terrible DX?

I also think HTMX is meant mostly for backend developers to be more productive in frontend.

Even with react, we have found that having a separate API layer was more ergonomic.

Maybe with graphql it is different

B25 for Bloom would've been nicer

Yep. BQ,GKE, and at a metalevel the simpler project structure -all have been great. I cannot still fully understand the org hierarchy that AWS has yet.

I'm probably an outlier here. My experience with GCP support has been nothing but stellar, like I described in another comment down below

I've had similar experiences with Google as well. Reaching out with new services, hours with some of their technical people, invites to meetups, free credits, an extremely pleasing and responsive account manager. We spend a few hundred thousand dollars a year with them. The actual software is top notch. Most haven't been just turn it on and forget it.

Do you do this in raw react, or use some third party carousel library? If so, maybe something like that can be used with HTMX as well?

But your larger point stands, HTMX is probably not a great fit for highly interactive webapps, even though you can push it pretty far

More often than not, forms are the database model. They very frequently evolve together. The entire data transfer object to model copy back and forth is unnecessary most of the time

Spring boot has form validations pretty much out of the box, via validation annotations.

I have had a similar experience with their API. Very verbose json structure, lack of stable row IDs, inconsistent data types. And being a spreadsheet, it also has to have styling/formatting details, complicating it even more.