> Don't just believe that because something is trendy that it is good
The JS community would do well to listen to this advice. I see a lot of JS developers choosing a library or framework without putting a lot of thought into considering the long term tradeoffs of using such dependencies. This is acceptable for side projects as they're done for learning, but it's irresponsible if you do this for production codebase.
It saddens me that the choice of a tool is driven by resume or coolness factor rather than being the right tool for the job.