Thoughts on React vs. Vue vs. Everything Else in 2023
chrlschn.medium.com
Thoughts on React vs. Vue vs. Everything Else in 2023
1–10 of 44 posts
Re: Thoughts on React vs. Vue vs. Everything Else in 2023
#2> developers need to be more vigilant with React code as
> articles on managing this complexity that every React developer should read
Here's the thing. You can do your best to spread how things ought to be done and what people should be doing. The majority of developers are not going to be vigilant, nor are they going to read these, nor does it occur to them that they're being suffering from its complexity. In a way it's similar to git - people use git because other people use git. It lets you get into difficult situations. The difference is that git also lets you get out quickly. Web codebases are not so forgiving, a lot of mistakes can be forever as it's costly to unwind.
I've encountered this a few times before realizing we were doing a lot better with Angular. It's not as popular, and its complexity does not grow as fast. Similarly for Vue as the author noted.
> but I do sense that there is a growing wave against the complexity brought forth by the current champs.
I certainly hope so, but I'm not seeing it. The industry seems to prefer the most complicated solution in different areas. k8s has won the orchestration mindshare and demonstrates a similar pattern of complexity and maintenance.
Re: Thoughts on React vs. Vue vs. Everything Else in 2023
#3Svelte is still the best by just about every metric that matters. The consensus seems to be clear that once you get a real taste of the Svelte DX, everything else is a downgrade.
Re: Thoughts on React vs. Vue vs. Everything Else in 2023
#4Every time I try to do something with modern JS I'm reminded of this blog post (https://peterxjang.com/blog/modern-javascript-explained-for-...)
And also every time I end up giving up because it's so damn complex
Re: Thoughts on React vs. Vue vs. Everything Else in 2023
#5Svelte is still the best by just about every metric that matters. The consensus seems to be clear that once you get a real taste of the Svelte DX, everything else is a downgrade.
Except the job market and/or trying to hire svelte developers.
Re: Thoughts on React vs. Vue vs. Everything Else in 2023
#6Dealing with url-driven /query-params in react... I miss ember. So much.
Re: Thoughts on React vs. Vue vs. Everything Else in 2023
#7With H/3, modern frameworks have become unnecessary deviations from web standards that result in high costs and lower app lifetimes. Do standard server side work, don’t use node as a server, sprinkle a bit of typescript where needed, and keep things lean.
As a recovering front end developer of 20 years, someone who has played with every damn framework and used most of them professionally; just stick to web standards and ignore the frameworks unless you specifically need them.
For example: we are using HN. It is simple. It works. It does not need to change. It does not need to be reddit or twitter or whatever, to be engaging. It’s good because it’s focused simple and well maintained. Almost every app I enjoy that has been over complicated or lost touch with its user base has done so while implementing these frameworks. They are business death. See; Facebook (react destroyed fb), Google (angular destroyed AdWords and G Suite), and so on. You lose analytics, accessibility, performance for the end user, less server side bugs is bad when clients are running the bugs, and most importantly you lose track of your customers needs.
If you want your shit to work, keep it close to the metal, conform to standards, scale only where necessary, and listen to your customers.
Re: Thoughts on React vs. Vue vs. Everything Else in 2023
#8Dealing with url-driven /query-params in react... I miss ember. So much.
Still have an Ember app that was last touched in 2016 other than library updates working perfectly in production earning millions of dollars. The React replacement we struggled with took many man-years longer to develop and is still not as easy to deal with.
With Ember we went through the entire 2 way binding -> DDAU transition in the middle of developing the app (and many other transitions, since we started with a pre 1.0 version of the framework), but the core team did such a fantastic job of making the transition as easy as possible that I don’t have a single nightmare from those days. In fact it seemed completely uneventful.
Re: Thoughts on React vs. Vue vs. Everything Else in 2023
#9Svelte is still the best by just about every metric that matters. The consensus seems to be clear that once you get a real taste of the Svelte DX, everything else is a downgrade.
Except the job market and/or trying to hire svelte developers.
Yea but any web dev can learn Svelte in a weekend which is a huge advantage.
I’ve been making a living as a freelance Svelte dev for years now and never struggle to find work, but your point stands — job market share matters.
Hopefully (for devs, execs, and users sake) Svelte adoption will continue to rise!
Re: Thoughts on React vs. Vue vs. Everything Else in 2023
#10With H/3, modern frameworks have become unnecessary deviations from web standards that result in high costs and lower app lifetimes. Do standard server side work, don’t use node as a server, sprinkle a bit of typescript where needed, and keep things lean. As a recovering front end developer of 20 years, someone who has played with every damn framework and used most of them professionally; just stick to web standards…
Your example does not align with your closing statement. Using Arc is certainly not "sticking to web standards" in the way you're proposing.
HN is simple and works, from a user perspective. I don't have my hands on the codebase, but I imagine it's kind of fun to work on precisely because it isn't "close to the metal". DX is just as important as UX is, you have to strike a balance.
Not sure there's much correlation between frameworks and apps becoming complicated or losing touch with their userbase. Using AdWords as an example, I'm like ~75% sure they went from one framework (Google Web Toolkit) to another (AngularJS).