I kind of agree.. Libraries per se are not the problem. They are there to solve a pain point in most cases. The problem, IMHO, comes when when we try to use a library or idea just because it's trendy without checking first if it fits our current domain.
Sure, react-redux by example is a great implementation of the suscribe-publish pattern. However abussing libraries is prior to become a library fanboy. Recently saw a video of someone adding lodash to calculate 1 time an average. That is not using the most importanr skill in dev, solving problems. Lodash could be usefull in any project with several instace of use, but importing it for only 1 case of use?
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.
The root problem is Javascript development culture, using libraries for everything halts down the problem solution proccess
Completely agree with this comment. We lose some of the basics of development when we so strongly depend on libraries and frameworks.
I kind of agree.. Libraries per se are not the problem. They are there to solve a pain point in most cases. The problem, IMHO, comes when when we try to use a library or idea just because it's trendy without checking first if it fits our current domain.
Sure, react-redux by example is a great implementation of the suscribe-publish pattern. However abussing libraries is prior to become a library fanboy. Recently saw a video of someone adding lodash to calculate 1 time an average. That is not using the most importanr skill in dev, solving problems. Lodash could be usefull in any project with several instace of use, but importing it for only 1 case of use?