The analytics people didn’t even know where these users were coming from. Of course, your javascript-based analytics package doesn’t see the users you are bouncing because of javascript failures.
I explained what I had built to my replacement, that it always worked even without javascript. He was appalled and said, “but that’s a lot more work for us.”
Bullshit. It’s absolutely not more work than React. He just isn’t familiar with the tooling the browser natively provides.
When your entire code base is in typescript and you have multiple people working on it, straight HTML feels like stepping backwards in time. Just because it’s possible to do a lot of interactivity without React doesn’t mean it’s simpler or easier for the team
If “it feels old” is your method of judging coding frameworks, I don’t know what to tell you.
Anyone who can do typescript/React already has to do HTML anyway, there’s very little to learn. Unless you are making extremely interactive stuff, there’s no reason to overcomplicate things. This article’s task, for instance, was a simple form submission.
And all this is of course ignoring the massive security disaster that is going on in the js/ts world right now. Guess what never seems to have supply chain vulnerabilities? Pure HTML.
A part of me agrees with you, however, the forced structure of components does tend to remove some of the opportunity for accidentally breaking other people’s functionality. Usually. That said, React is a huge pain in the ass, and often. And keeping npm dependencies up to date is a fuckin hassle. I should know, that’s one of the roles I’ve taken on, and it sucks.
Agreed, I totally love web components. And there’s no vanilla way to do them elegantly. (And that’s a real tragedy.)
I just have an aversion to overengineering things. The vast majority of websites are predominantly read only, and would work better as a simple (mostly) static site.
I just have an aversion to overengineering things.
This is me exactly ^
Currently a team mate is rewriting something I built which was simple and worked, and was just slow. It’s an internal tool, and what we’re doing is expected to be slow. So it annoys me a lot that they are now making it needlessly complex when the way I did it was not ideal in performance but worked. The service is gonna be used like 30 times per week. He’s gonna spend a week and add complexity/maintenance to save $15 a month in cloud computing… I hate it.
Breath of fresh air, this.
I don’t know how UI design is taught in school, etc. but this should be it. It’s clear that it’s not, or the designers are being forced by the people with money to ignore what they’ve been taught.
Idiots with money ruin everything. Don’t give idiots money.
Html? What type of AI is that, “here’s the machine learning!”…?
Using web technology as intended? How revolutionary.
… form submissions and redirects took a while to explain to my colleagues, on account of everyone being used to heavily client-side web applications.
We are so cooked
