2 ms·
One view I have is that the frameworks are a necessary learning phase for many developers. Does anyone remember AngularJS v1? That was my first web framework.
by bob1029 3y ago
One view I have is that the frameworks are a necessary learning phase for many developers.
Does anyone remember AngularJS v1? That was my first web framework. I reached for that when I saw a demo of a UI that was close to what we wanted for a product. I had no clue how to do web layouts in 2015. I made it through Angular V2, RiotJS and then Blazor for a few years before going totally vanilla with basic SSR and form posting.
The analogy of comparing these frameworks to training wheels is still the most apt one in my mind. For many developers, having a little bit of a shim to keep the bike upright while you are learning how the pedals and steering work can do wonders for the learning experience. But, after a while you may find the training wheels start to cause frustration and get in your way. The hardest part of all of this is deciding when to do away with them.
Vanilla web (as rendered on the server) has always been the most rational path for open web development, but it only recently got to a point where it may be the best place for a novice to start. Raw HTML/CSS/JS in 2024 is not like it was in 2016. We may be entering a phase where frameworks arent even necessary as a learning tool. Flexbox and friends do a lot of fucking damage compared to what we used to have not even a decade ago.
- kevindamm 3y agobut IMO it should be the other way around -- learning the core of the tools from experiments in vanilla web, then when projects get big enough or when joining a team of developers go to the frameworks to help manage the multiple moving parts and concurrent merges. Sure, components can help with that without having to lean on a framework, but a framework can help align the opinions of the frontend design.