Discover more from Chris Minnick's Substack of Curiousity
If you're working for someone else, the tools you use will be dictated by your employer, the client's existing technology stack, the skills of your co-workers, and a ton of other factors. Dropping your current framework because of the prevailing sentiment among guys with crazy haircuts on YouTube isn't a luxury most developers have.
The rise and fall of popularity among tools is a natural thing in an environment where no one really has the foggiest notion what the best way to make websites is. Web developers seem to be stuck in a loop from static websites, to server-side rendering, to client-side rendering, to some hybrid between the two, and back to static websites. We've been around this loop several times now. Each time around the loop, the tools get more sophisticated and more complex. In some cases, they even get better. Until we figure out something that actually works, we're going to keep going around the loop.
There is an alternative that will not only make you able to quickly learn and become an expert with the latest frameworks and tools, but also ensure that you'll always be one of the cool kids. Are you ready for it?
If you know what your framework of choice is doing behind the scenes, you can write good code with the library much faster than without it, which is the whole point of using a library in the first place.