4 ms·
Dunno, if you need to be convinced to use a tool, then maybe you aren't yet in the market for said tool. I think it's a cherry on top to describe use-cases but
by always_good 9y ago
Dunno, if you need to be convinced to use a tool, then maybe you aren't yet in the market for said tool. I think it's a cherry on top to describe use-cases but not so critical that there's some sort of ecosystem problem that you describe.
- deleted 9y ago[deleted]
- BigJono 9y agoThe purpose is to un-convince people from using it. Way too often people have already made up their mind by the time they reach the docs, based purely on how popular the tool is, how flashy the front page is, or whatever bad advice they've received from someone who feels the need to justify their library of choice.
- tjholowaychuk 9y agoIt's good to have critical thinking skills, if people can't figure out if they want to use a tool or not, they should probably work on that a bit!
- BigJono 9y agoFor sure! Doesn't mean we shouldn't strive to give them a helping hand though. I know I fell victim to the exact same problem when I was learning front-end dev. I'm sure everyone in that space has had a "why on earth have I been using this for the past 6 months?" moment for one library or another. I just feel like we should be taking more preventative measures against that.