4,375 karma · joined November 17, 2022
info at pretty diff dot com
Cheneys Law:
When it comes to frameworks (any framework) any jargon not explicitly pointing to numbers always eventually reduces down to some highly personalized interpretation of easy.
meet.hn/city/32.989468,-97.28243145646596/Fort-Worth
How would you know? You are choosing conventions over measures. If you measure nothing you have no idea what is faster or not. I have been doing this work for nearly 20 years and many JavaScript developers claim measuring things is easy, but they never do it. When pressed on it they never have and don't know how. Instead they guess at performance to reinforce their own preferences. I have an autistic kiddo that does this and everybody sees right through it.
If you operate purely from convention then what does it matter if I did show you my code? What do you hope to gain from looking at something you have already dismissed in advance?
Also, the framework worship is always a bit bizarre to me because the front end of even the largest of single page applications is relatively tiny compared to the supporting back end. If a developer is writing the entire application then why invest so much effort into over engineering such a small slice of the total code? It isn't productive unless it is the maximal extent of a given developer's capabilities.
https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-a...
Really though these layoffs have been more than 20 years in the making. There are some incredibly brilliant people out there writing original solutions to challenging problems. And there are people who cannot do more than put text on screen using a JavaScript framework. There are so many people hired to write software who cannot write software.
My large SPA achieves full page load with state restoration in under 150ms. You don’t need React or components to achieve simplified state management.
Part of the foolishness here is that you are convinced your approach is faster but you have no idea what my approach is. You certainly aren’t measuring anything so even if you were aware of my approach you are still just randomly guessing at the result.
Component systems are the new OOP. They are numerically complex. People think they are all the rave and I don't know why, but then people also think OOP is generally all the rave and I don't think they know why.
You don't need component systems, but if you choose to go down that path just realize everything is far more work because there is tremendous amounts of duplication both explicitly in your logic and under the hood where you are not looking. Most people who believe they need this are locked into an enormous framework and deliberately avoid looking under the hood, because its a giant scary beast they believe they cannot live without.
If you want simple you will do everything in your power to avoid component systems, because simple does not mean easy. Rich explains it better in what might be the best computer science talk ever given: Simple Made Easy
I suspect your point is that Angular or React must exist as the primary work product for a team to operate, but why? Are you suggesting that nobody is capable of writing software without a third party framework to tell them what to do? To me this sounds like you have absolutely no idea how to program or that you have no faith that anybody can program original solutions... except for the people who invent large frameworks.
Ad hominem literally translates as "to the man". It is a direct attack on the person in conversation instead of the subject of conversation, which does not apply on nameless third parties.
Your comment completely reaffirms my original comment way at the top in that these frameworks largely exists so that employers can avoid any kind of investment in their developers.
It helps when you write software other people want to use and provide good enough documentation.