421–430 of 520 posts
. > looking for a nice framework for website > ask dev if their framework is hypermedia or javascript > doesn't understand, pull out long essay on hypermedia as the engine of application state > dev laughs and says "its a good framework sir" > check github > its javascript
hi there, as many of you know, i am the creator of htmx and I'm happy to answer any questions about it htmx has seen a surge in popularity, triggered by a video by fireship dev ( https://www.youtube.com/watch?v=r-GSGH2RxJs ) and a series of videos by ThePrimeagen, a popular twitch streamer on it hacker news readers might be interested in the essays I have written on htmx & hypermedia in general here: https://htmx.org…
I've enjoyed using htmx and created a simple library in golang to help out. Here is an example app https://github.com/pyrossh/gromer/tree/master/_example
Earlier quoted context omitted.
Many of the ideas and concepts in htmx are things we worked on starting around 2012 at a top tier investment bank. Implementation details differ quite significantly, but the idea of hypermedia driven applications was core to everything we did. We unfortunately weren't able to win hearts and minds around these concepts in the long run, and blog driven development (a.k.a. cargo culting) replaced our efforts. I feel som…
> blog driven development (a.k.a. cargo culting) replaced our efforts Ironic considering what the OP attributes to HTMX's current popularity.
Earlier quoted context omitted.
I don't think using the accept header is a good idea. The main reason is that it doesn't necessarily play well with proxies. Most notoriously, Vary: Accept is not supported by Cloudflare (with the exception of images). This means it's not safe to use the accept header if your site will ever be backed by Cloudflare, as you could end up returning cached HTML to a JSON client or vice-versa. https://developers.cloudflare…
I’m not a fan of vendors “not supporting something” as a reason to not use something. Either get a new vendor, put pressure on the vendor, or ignore the feature you want to use. I personally don’t care about what cloudflare does because I don’t use them. The rest is RTFM for whatever API you are calling and you usually have to send auth or cookies anyway, so an accept header isn’t that big of a deal.
I've been a HTMX fan "since before was cool".. Very happy for the recent attention and "success". Also enjoying the shitposting and backlash mostly from the front-end crowd who believe the Web was invented in 2013 and they "made that city". :) I'm biased since the time Backbone.js came around, I understood part of the pain but was moderately skeptical, fast forward to React with the young energetic bros building dead…
I hear you're buying a synthesizer and an arpeggiator and are throwing your computer out the window because you want to make something real. I hear that you and your band have sold your guitars and bought turntables. I hear you rewrote your http endpoints to return JSON because that was REST. I hear that you and your band have sold your turntables and bought guitars. I hear you rewrote your http endpoints to return t…
A sense a lot of familiarity
Earlier quoted context omitted.
You can check this talk out https://youtu.be/3GObi93tjZI I was thinking the same but in the video they specifically talk about faceted search and how they did it with htmx. For the second part you probably go with your own javascript or get away with hyperscript
That is the talk I've watched before coming to the above conclusion. The faceted search demonstrated in the talk is still an order of magnitude simpler then what I have build. It is still a cool example of what you can do with htmx and it certainly pushes the envelope but the UX choices are dictated by what is possible in htmx. I also think that the talk is somewhat dishonest, it is by a backend developer that want t…
If you replace a 22,000 LOC React + Python app with 1,000 LOC of whatever framework you choose, I would be very, very, very, very impressed. I don't believe you.
There are many applications where htmlx is objectively the best tool. But i really hate all the hype around it and people pushing it as react replacement.
Earlier quoted context omitted.
>The fact your HTML barely reads like HTML after Tailwind, and reads more like your file is corrupted is I guess not mentioned in the tagline. Not my experience for the record. I use Tailwind in my side project, and it is exactly as convenient as it sounds to write my styles directly into HTML rather than think of a class name, add it in HTML, switch to the proper CSS file (or create it if it doesn't exist and make s…
I’ve messed around with tailwind a bit now, and honestly I could never use it in even a moderately complex site without some sort of “component” framework. I think you’re talking about just serving a .html file for every page in a site right? Having all of your styles duplicated everywhere would be much more confusing than writing CSS (and having to invent one name per groups of common things.) IMO it’s only viable i…
It's implicitly expected you're already doing so, such as web components or whatever your selected framework uses to abstract components.
> Having all of your styles duplicated everywhere
Locality is a feature. It's much easier to jump into any random bit of HTML and understand what's going on and confidently make changes without having to pull up multiple other files to grok the classes involved.
Compression is going to solve most of the issues with repeating classes everywhere, and while not recommend you can still use something like Sass/SCSS and Tailwind directives like @apply to separate classes into their own files.
.my-class {
@apply p2 mr-4 mb-2;
}