Live data from Hacker News

Htmx 2.0.4 Released

github.com

51–60 of 136 posts

Re: Htmx 2.0.4 Released

#51
post #42

Earlier quoted context omitted.

Harsh dude, why not just keep quiet?

Sick and tired of any server-side rendering of web pages. If you don't have to deal with incident response you can be quiet. It doesn't scale and it complicates meeting any client requirements. Get this trash outta here. For real.

and yet here we find ourselves, exchanging our server side rendered opinions on the matter

Re: Htmx 2.0.4 Released

#52

Earlier quoted context omitted.

> Changing the default behavior feels like a breaking change I'm fine with breaking changes personally. An adherence to maintaining backward compatibility always is what leads to bloat and criticisms of "poor design" from HNers in the future. Keep it slim, have one way to do things, and avoid the disaster that is js and python today.

How is Python a disaster?

[deleted]

Re: Htmx 2.0.4 Released

#55
post #48

Earlier quoted context omitted.

What happens when your static stie infrastructure goes down? I fear your argument is turtles all the way down. Edit: I'll show this to my boss. I'm sure he'll get a chuckle.

I hope he does because that's a huge sign your entire management structure is super out of touch and I hope you're next DOR or incident ressponse reveals the truth.

May the truth set us all free

Re: Htmx 2.0.4 Released

#56

Earlier quoted context omitted.

Sick and tired of any server-side rendering of web pages. If you don't have to deal with incident response you can be quiet. It doesn't scale and it complicates meeting any client requirements. Get this trash outta here. For real.

and yet here we find ourselves, exchanging our server side rendered opinions on the matter

Each comment should be entered into the code then committed. That commit then should trigger the CI build. That should then upload the static assets to the CDN. It's clearly the optimal solution.

Re: Htmx 2.0.4 Released

#57
>htmx.ajax, htmx:trigger, synthetic load event

>Nested shadow root

>element is reinitialized via htmx.process()

>Boosted tags

>htmx-powered elements located outside a form, but that refer to a form via the form attribute

>preload, hx-boost, response-targets, ws, head-support, sse

I see... Folks at HTMX are always thriving for a little bit more power of hypertext.

Remember guys this is how S.I.M.P.L.I.C.I.T.Y. looks like.

Fnatics, unleash your downvotes!

Re: Htmx 2.0.4 Released

#58
post #42

Earlier quoted context omitted.

Harsh dude, why not just keep quiet?

Sick and tired of any server-side rendering of web pages. If you don't have to deal with incident response you can be quiet. It doesn't scale and it complicates meeting any client requirements. Get this trash outta here. For real.

    Sick and tired of any server-side rendering of web pages.

If you don't have to deal with incident response you can be quiet.

It doesn't scale and it complicates meeting any client requirements. Get this trash outta here. For real.

Ummm... do you know where you are? Do you know how this works? Hint -- try "view source" right now. I made it easy for you by pasting a random snippet above...

Re: Htmx 2.0.4 Released

#59
post #42

Earlier quoted context omitted.

Harsh dude, why not just keep quiet?

Sick and tired of any server-side rendering of web pages. If you don't have to deal with incident response you can be quiet. It doesn't scale and it complicates meeting any client requirements. Get this trash outta here. For real.

Imagine being this delusional
Post reply on HN