A really big problem with web app dev is that it covers a very broad area.
Advice like not using libraries will have very polarized reactions (as evidenced by this thread) based on what kind of goals people are working on. Some react projects are very short lived so common problems like a library no longer being maintained are a non-factor. For large scale projects, typing loc is not a bottle neck, changing a foundational library that everything is based on is a potential massive timebomb.
And then there's all the decisions (like a date picker) where it can go either way.
Of you are not using libraries, the smallest of the projects will become a large scale project.
I prefer having to keep up to date with libraries than having to deal with tons of some "smart ass" reinvention of the wheel that doesn't have documentation and tests and it's full of bugs and corner cases.
The code you write yourself also requires maintenance.
Advice like not using libraries will have very polarized reactions (as evidenced by this thread) based on what kind of goals people are working on. Some react projects are very short lived so common problems like a library no longer being maintained are a non-factor. For large scale projects, typing loc is not a bottle neck, changing a foundational library that everything is based on is a potential massive timebomb.
And then there's all the decisions (like a date picker) where it can go either way.