I feel you, but the React stack nowadays is so deep and diverse that it feels like it’s gonna be soon affecting browsers’ architecture. They literary solved all the hard problems in a rather elegant way. I compare to my days with PHP3 and jQuery 🙂
It basically made functional UIs mainstream, which greatly improved testability, and correctness.
I do remember the millions of websites/small GUIs where you could easily end up in inconsistent states (like a checkbox not being in sync with another related state) and while UI bugs are by no means “over”, I personally experience less bugs of this kind.
(Unfortunately, API calls are still a frequent source of errors and those are often not handled properly by UIs)
The content of this article doesn’t fully resonate with me. I think when you build your own personal website you are free to overcomplicate as much as you want. Some people use that to have fun and as a way to gain knowledge into something you wouldn’t normally have the chance to do it at your work. If it’s all about minimizing work, you are better off using one of the several blogging platforms out there.
Maybe the real lesson here is that using 25ish different technologies to generate a simple HTML site is not “perfect”. To be honest, I didn’t understand the article at all until I realized this what was the author implies.
Good enough is the real enemy of good
Another topic for another post!
good enough is the enemy of all change. Terms and conditions apply, do your own risk assessment before changing tech stack, yada yada
then it’s not good enough ;-)
I was furious for a couple of seconds.
I feel you, but the React stack nowadays is so deep and diverse that it feels like it’s gonna be soon affecting browsers’ architecture. They literary solved all the hard problems in a rather elegant way. I compare to my days with PHP3 and jQuery 🙂
While my blog is in PHP. I really enjoy React actually. Also, I very much like this component library: https://mantine.dev/
I don’t think it’s elegant by any means. In practice.
It basically made functional UIs mainstream, which greatly improved testability, and correctness.
I do remember the millions of websites/small GUIs where you could easily end up in inconsistent states (like a checkbox not being in sync with another related state) and while UI bugs are by no means “over”, I personally experience less bugs of this kind.
(Unfortunately, API calls are still a frequent source of errors and those are often not handled properly by UIs)
Why not? Any points against? What would you use for complex web apps?
I mean react itself, not your particular pick of options inside that stack.
React itself is also cool.
I guess the author did not consider the solution to be perfect, because perfection would have been a static site generator + rsync :).
Well, PHP feel very static =)
…with dynamic parts.
The content of this article doesn’t fully resonate with me. I think when you build your own personal website you are free to overcomplicate as much as you want. Some people use that to have fun and as a way to gain knowledge into something you wouldn’t normally have the chance to do it at your work. If it’s all about minimizing work, you are better off using one of the several blogging platforms out there.
None of them have comments and page views. WordPress only.
Maybe the real lesson here is that using 25ish different technologies to generate a simple HTML site is not “perfect”. To be honest, I didn’t understand the article at all until I realized this what was the author implies.