As with almost everything in development, it depends.
Developing without a framework is possible, but it does not make much sense to do it, unless the frameworks that exist do not meet your needs.
The open source framworks grow as we all contribute, some simply contribute using them and reporting their issues and others get their hands dirty and solve those issues. That teamwork is worth appreciating, there are few professions where you see that.
In any case, sometimes it is necessary to write from scratch. It happened to me when I do not feel comfortable with the "settings" chosen in a library.
In general, I use the frameworks to work and the code from scratch to learn.
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
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.