"Do not try to reinvent the wheel... "
I agreed on somewhat, many time a project does not need framework, because it could led to a situation of "Use a cannon to shoot a bird".
But many framework safer and could be faster solution - and more accurate - than most of the people able to build. A very good use-case when people would like to implement their own routing solution instead of using a micro framework or even just a routing package.
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
At business level it's not called reinvent the wheel, it's analyzed to see if it fits exactly with the needs of the company. If you got that the needs does not match exactly with what is done, you'll need to do by your own. This is because you need to modify it from the beginning and at long time app lifecycle you'll need to patch many things. Imagine building a project with 15 different libs (it's not that crazy, I saw big projects with much more than that) and then 1 lib gets out of support, then another one, then another... you'll need to be aware of any bug found on your version (latest) and patch it by your own, while making the things by your own and adding a security audit into your app development cycle makes your app more secure.
Of course frameworks need to be used depending on the situation, for example you will not be using react, angular, preact or svelte for a landing page but for a back office private control app. You'll use html, css (sass/scss) and few js as possible for a landing page or static views on the front office and the tools may vary for the "business public views" (those who makes your company make money) depending on the needs.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
"Do not try to reinvent the wheel... "
I agreed on somewhat, many time a project does not need framework, because it could led to a situation of "Use a cannon to shoot a bird".
But many framework safer and could be faster solution - and more accurate - than most of the people able to build. A very good use-case when people would like to implement their own routing solution instead of using a micro framework or even just a routing package.
You're right and I agree with that. We don't need to reinvent the wheel if it's not for purpose of learning.
At business level it's not called reinvent the wheel, it's analyzed to see if it fits exactly with the needs of the company. If you got that the needs does not match exactly with what is done, you'll need to do by your own. This is because you need to modify it from the beginning and at long time app lifecycle you'll need to patch many things. Imagine building a project with 15 different libs (it's not that crazy, I saw big projects with much more than that) and then 1 lib gets out of support, then another one, then another... you'll need to be aware of any bug found on your version (latest) and patch it by your own, while making the things by your own and adding a security audit into your app development cycle makes your app more secure.
Of course frameworks need to be used depending on the situation, for example you will not be using react, angular, preact or svelte for a landing page but for a back office private control app. You'll use html, css (sass/scss) and few js as possible for a landing page or static views on the front office and the tools may vary for the "business public views" (those who makes your company make money) depending on the needs.