by alfonsodev on 12/12/23, 11:19 AM with 79 comments
by coolhand2120 on 12/12/23, 8:07 PM
5-7 second skeleton loaders are there because backend systems are slow, not because of the front end application. You can say "oh but you can pre-render", but there are times when you can't. You could render the whole thing on the backend, but then you'll wait 5-7 seconds at a white page vs. progressive loading. Whatever is taking 5-7 seconds (LCP) is not going to get faster for you in your region by some magical front end dance.
Not every business is the same and no one solution will work for everyone. And concluding that we should "go back to jQuery" really speaks volumes of the author. jQuery was not "the good old days".
The problem with FE is that they seem to be wannabe nodejs BE devs instead of the W3C experts they should be. If FE devs focus on web standards and less on Rube Goldberg machines they would be well served.
by miki123211 on 12/12/23, 9:39 PM
As a screen reader user with no way to read words written on paper (short of getting a scanner and spending hours on putting books through it), I have to look for alternatives. I hate it when authors do this. I get why, but it's still frustrating.
There's also the fact that the author of this article decided to embed X posts as unlabeled screenshots for some unknown reason. This breaks accessibility, copy/paste, translations, flexible screen layouts and probably a bunch of other things I'm not aware of. Putting text in images is never a good idea, much less so when there's a perfectly fine embeds API for GOd's sake.
I'm really saddened to see somebody who claims to care about web standards be so dismissive of accessibility concerns.
by eddd-ddde on 12/12/23, 7:14 PM
Someone that does not understand sanitisation boundaries has no business working on web development. This is how you end up with html in your database, people just render whatever piece of data because it "just works" in frameworks like react (I've seen it myself in production).
by snowstormsun on 12/12/23, 9:13 PM
Author does not seem to understand the concept of XSS. Of course your own API could return user-provided data to trigger XSS attacks. Entering <script>alert(1);</script> in a messenger to see whether its rendered value is escaped correctly is a famous example.
by sshine on 12/12/23, 9:13 PM
Since we're bashing dumb comments with dumb comments, the Twitter comment is actually saying:
over 25,000 hours
Assuming
- 5 weeks of vacation each year
- 8 hours of work, 5 days a week
(52 - 5) * 5 days * 8 hours * 15 years = 28.200 hours
by jlundberg on 12/12/23, 7:54 PM
by masfoobar on 12/14/23, 3:56 PM
Generally speaking - when you make an HTTP request - you are likely returning:
XML <root> <users> <user> <id>1</id> <name>foo</name> </user> </users> </root>
[or]
JSON { "users": [{ "id": 1, "name": "foo" }] }
[or]
HTML: <div class="users"> <div class"user"> <span class="user-id">1</span> <span class="user-name">foo</span> <button class="btn btn-small">edit</button> </div> </div>
[When using HTMX, you would add some additional tags. You are still just returning HTML]
<div class="users">
<div class"user" hx-target="this" hx-swap="outerHTML">
<span class="user-id">1</span>
<span class="user-name">foo</span>
<button hx-get="/user/1/edit" class="btn btn-small">edit</button>
</div>
</div>
I guess responses is more in line with -- "they tooook our jooooowbs!"
From what I read elsewhere. "React creates jobs. HTMX doesn't"
by moritzwarhier on 12/12/23, 8:50 PM
I think every developer who has worked using a CMS using traditional templating + "ajax" has reinvented parts of it at some point in their career. At least I have.
If I would find myself in this scenario again, I'd gladly reach for htmx.
Apart from the social media observations, topics tend to be random here, but I like train-of-thought writing.
by troupo on 12/12/23, 10:21 PM
Does it have its merits? Maybe? I don't know, I can never get past the memes and shit-slinging. Or past them superficially co-opting terms they have nothing to do with like Erlang, or hypermedia.
It's a toy mascarading as a serious tool.
by slj on 12/12/23, 8:54 PM
by davedx on 12/12/23, 9:03 PM
But you can't hand-wave the security concerns of that away by ridiculing the people trying to discuss them.
There is a fundamental difference between your server returning data versus returning code. If you don't want to accept that, fine, it's your project, or career, whatever. But if you conduct extensive ad hominems against people (I'm not a fan of "Devrels" but jeez, that part of this post felt like blatant character assassination) instead of just debating the facts then you're a douche and no better than the people you're disparaging.
I think HTMX is an interesting project that I'll probably give a try at some point. But breathless cultish hype of it has already turned me off. I don't even know if React got this much attention!?
by qwertthrowway on 12/12/23, 8:55 PM
by gabrieledarrigo on 12/12/23, 11:27 PM
Ps: Nathan James, pls stop
by _dain_ on 12/12/23, 8:55 PM
by nesarkvechnep on 12/12/23, 7:43 PM