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.
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.
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.