> This is, unfortunately, part of the culture of front end development right now: sky-high levels of complexity are tolerated in application frameworks, in build tool chains, in deployment models and so on, and, when problems arise due to all this complexity, more complexity is often offered as the answer.
> "Simple" is disparaging and "sophisticated" is high praise.
So, rather.
There was a series of similar Twitter discussions when a popular JavaScript "influencer" published an article[0] on how they built their website. The amount of complexity that is self-inflicted in the said article was obviously enormous for proponents of MPAs.
However the JS community mostly echoed that the complexity was absolutely within norm. The cultural chasm between JS developers and people who push for simplicity was huge. And the refusal to admit the unnecessary complexity was nothing short of Stockholm Syndrome, imho.
[0] https://kentcdodds.com/blog/how-i-built-a-modern-website-in-...
This was the HN reaction to the article:
I've been working recently on two code bases: one using angular and the other htmx (with python/jinja2/FastAPI). Both aiming to deliver broadly comparable interaction - so approximately comparable in essential complexity.
In a month, or a year, I'm confident I'll be able to check out the htmx app and work with it pretty much right away. The dependencies won't have changed much; the build will still work; and I'll be able to understand the code. I will lay bets now that the same will not be true of the angular app. On any one of those three counts.
If simple, understandable, stable and effective are what GPP meant by "primitive", then I want more "primitive" tools like htmx.
Light sabres, not death stars.
Yet another cheap shot. Might as well say 'fu js devs'. How come every time we have a thread on this thing its devs and supporters always come across as arrogant, bitter folks with an axe to grind.
I don't like your technology. I didn't like it several years ago when I was introduced to it, and I don't like it now. It's not a bad idea but calling me an idiot for not doing UI on the backend is not going to win over anyone that doesn't already hate js and the people who write js.
People seem to act like those problems just "go away" when you don't do SPA but it doesnt.
It seems the backend community mostly echoes that the complexity is absolutely within norm. The cultural chasm between backend developers and people who push for simplicity is huge. And the refusal to admit the unnecessary complexity is nothing short of Stockholm Syndrome... imho
You don't need jumbo jet to deliver pizzas locally.