If only comparing frameworks to something scratch built, frameworks do compare favorably. However, there is a 3rd choice that is typically even better: libraries. Take React for example. One of the reasons for its popularity is its virtual DOM rendering. Most people are on about the (frameworky) components, but the rendering library can be used in a lot of different scenarios. For example Microsoft's SAFE stack. The last two letters stand for Fable Elmish (which does not use components), and that actually uses the React rendering library for front end UI. Whenever you see things like React + Vue, it probably means the React rendering library is being used to solve the rendering problem.
Side note: one of your post tags is "scratchcoed". A simple misspelling, but it made me chuckle. I imagine someone who goes around scratching college students. :)
Hi, I'm John Samuel Obinna, Full-stack developer, proficient in Web technologies with over 5 years of experience developing scalable distributed applications
If only comparing frameworks to something scratch built, frameworks do compare favorably. However, there is a 3rd choice that is typically even better: libraries. Take React for example. One of the reasons for its popularity is its virtual DOM rendering. Most people are on about the (frameworky) components, but the rendering library can be used in a lot of different scenarios. For example Microsoft's SAFE stack. The last two letters stand for Fable Elmish (which does not use components), and that actually uses the React rendering library for front end UI. Whenever you see things like React + Vue, it probably means the React rendering library is being used to solve the rendering problem.
Side note: one of your post tags is "scratchcoed". A simple misspelling, but it made me chuckle. I imagine someone who goes around scratching college students. :)
Lol😃😃😃 I will fix it. Thanks