cont'd --- @User, these are extreme insults and serious allegations that you're directing at someone because of disagreements in what is basically a framework war. when i get into situations like this, i log off. i recommend the same. --- @\everyone, stop with the "js bad" shit. it's cringe and anti-intellectual. js is basically about as bad as all those other old, backwards-compatible languages that run everywhere. most criticisms of js also apply to hyperscript, and you seem to love that. don't make the lack of a skill your personality. the real bad thing about js is that the community is overrun with marketers and influencers (i do not believe Rich Harris is one of them). here at htmx, we may evangelize or propagandize, but we do not sell.

@gorgeous-airport-54386 👏👏👏🤌

👆

Just read the whole discussion 👆, along with most of the Twitter and hacker news action and I have to agree with @gorgeous-airport-54386: beating the “JS and JS frameworks are bad” drum won’t do us or anyone else any favors. Neither will Ignoring the accessibility crowd, hard-nosed as they may be. Getting into mud-slinging fests may be fun (and sometimes funny) and a way to let off steam, but again, long-term not doing anyone any favors. Let’s take this as a learning opportunity - clearly there are a few things we can do to reduce the amount of conclusion-jumping (unfair as it may be) that people make when they go to the htmx.org homepage looking for arguments against htmx. I also love the passion that some of you display (I hope the Cowboys won 😜), but considered, kind responses in a public, online debate is the best bet in situations like these.

Unless your name is @mysterious-toddler-20573, in which case ‘JS bad, hulk smash’ is just friggin’ hilarious 😂

(I cackled like a crack whore finding a $100 bill in her coat pocket at that one. Thanks for nothing @gorgeous-ghost-95789 )

> considered, kind responses in a public, online debate is the best bet in situations like these. i think carson did an alright job providing that. however, our community has a variety of people that differ in opinions and capacity for decorum, all ready to defend htmx. when that happens someone inevitably steps over a line and it rubs off on our reputation as a whole

although effectively telling accessibility advocates to "watch their tone" is not the best

Oh don’t get me wrong- Carson has the patience and demeanor of a saint, how anyone can get offended by anything he says on here/Twitter/hackernews/Reddit is beyond me.

we don't take ourselves very seriously, and that seems to tilt people who do

do they not know that computers aren't real?

Yup. Just like airplanes

Oh. The language is a lot spicier than I remember… sorry.. but still

Hey @gorgeous-airport-54386, look on the bright side… now you’ve got plenty material for the next “This week in htmx” 😁

how Carson feels about accessibility advocates is how other people feel when we talk about Roy Fielding

you're right, i should be stoking the flame not quelling it. i'm not being a good libelliste

This Week in HTMX Issue 9: Rich Harris Literally Wants Me Dead

/j

With the byline “but he has to wait his turn, just like everyone else”

Deadishness is a spectrum...

All in all, I say not bad. Twitter, after all, is not the Athenian agora. I learned a bit more about edge computing and v8. And there were some funny moments.

The Hn comments weren’t universally negative, quite happy with that!

Same energy as Spike in this clip 👍 💪 😂😂

@User I just wanted to say that from everything I have seen, you seem like a very talented, hard-working, level-headed and funny person. What a breath of fresh air. You will have a very successful future with your attitude wherever you end up. 10/10

Hi, I'm getting this error:

htmx.org@1.6.1:1 SyntaxError: Unexpected token < in JSON at position 0

I am returning HTML from FastAPI and this is the code:

response = '<div class="mr-2 w-3 rounded-full h-3 bg-red-500"></div>'
return HTMLResponse(content=response, status_code=200)

In my HTML template, this is what I have set up:

<div hx-get="http://0.0.0.0:8000/prep/node-status/?address={{ .Params.address }}" hx-trigger="load"></div>

It seems like HTMX thinks I am returning JSON, but my API is set up to HTML. Does anyone have any tips on how to get rid of the error?

I am coming from a pure backend part of the game, and I feel you: This Flask Tutorial from Miguel Grinberg IS the holy grail. I have never dealt with anything like HTML, Bootstrap, JS or whatsoever before and his tutorial motivated me to start - funny fact: I always thought "why do I have to put so much logic on my frontend, I want to do this on the backend", which I told colleagues and someone pointed me to "a very radical Frontend design idea called HTMX he read about"

But yes, communities evolve and grow around well documented, super accessible software, not technically the best softwares available.

@User perhaps your response headers have 'Content-Type' set to 'application/json' instead of 'text/plain'

i don't care about pointless virtue signalling.

"extreme insults and serious allegations" give me a break. you couldn't virtue signal hard enough if you were wearing plate armour and holding a bible.