this post was submitted on 16 May 2024
369 points (96.7% liked)

Programmer Humor

32572 readers
427 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] eager_eagle@lemmy.world 11 points 6 months ago (3 children)

my favorite JS framework is HTMX for making me write less JS or even none at all.

[–] MrPoopyButthole@lemmy.world 4 points 6 months ago (1 children)

Me too! I've been working with JS for more than 10 years but HTMX + Go has been a welcome transition.

[–] NuclearDolphin@lemmy.ml 1 points 6 months ago (1 children)

Wait are people writing Go for frontend code now? Or do you mean just replacing the node back end with Go?

[–] MrPoopyButthole@lemmy.world 3 points 6 months ago (1 children)

I was specifying my backend of choice to pair with HTMX.

[–] NuclearDolphin@lemmy.ml 2 points 6 months ago

Gotcha! I'll have to look into it. I heard of it being used with Rust, which is probably the only lang I want to use for backend anymore. If it minimizes JS boilerplate, that's a big win.

[–] rwhitisissle@lemmy.ml 4 points 6 months ago

I do a lot of systems and backend programming and HTMX is the only way I can actually be productive with frontend work when I have to do it. It's so simple and straightforward.

[–] NuclearDolphin@lemmy.ml 3 points 6 months ago (1 children)

I've heard nothing but good things about HTMX. I might have to play around just to get a feel.

[–] rwhitisissle@lemmy.ml 2 points 6 months ago

I’ve heard nothing but good things about HTMX

I've only ever heard anything "bad" about HTMX and it was here on Lemmy, actually. I ran into someone who was absolutely certain that HTMX was unsafe by design because it leveraged HTML over the wire and was therefore susceptible to HTML injection attacks, specifically by injecting malicious scripts that could be ran from domains you didn't control. I tried explaining that proper utilization of access-control headers innately prevented this because they worked on the browser level and couldn't be intercepted or interfered with by HTML injection by design, but he kept insisting it was unsafe while refusing to elaborate. He was very wrong, of course, but also very confident.