5 ms·
> So, to create any website, we need a framework, everyone knows this unquestionable truth. They lost me already. Is this supposed to be sarcasm? I'm hoping it
by codingdave 2y ago
> So, to create any website, we need a framework, everyone knows this unquestionable truth.
They lost me already. Is this supposed to be sarcasm? I'm hoping it is - the more I read, the more the entire article looks like they were trying to write satire... but then they end with a non-sarcastic conclusion.
I'm really unclear if this whole thing is satire or if they really just hate JS so much that they are over-exaggerating the most complex ways to engage with its ecosystem.
- ericmcer 2y agoI would say that is true for any web app with multiple contributors. If you don’t use an existing framework and try to just use js DOM methods you will end up creating your own framework eventually, but now no one understands it except you.
- stnmtn 2y agoThe main thing I find with articles that are anti-React is that they are saying React is bad when all you need is a pretty simple site with some dynamic elements. That's 100% true, it never hasn't been true, and any react evangelical will tell you the same thing. I would love to hear this authors take on if they would choose HTMX for a web app that is constrained to be highly-interactive, with multiple contributors/teams, and a dynamic user interface that requires heaps of internal state. I would assume the counter-argument would be, "something like that should not be on the web!", but unfortunately we are in a world where that is what customers expect for certain classes of application.