3 ms·
I'm a C# developer who has been learning React for the past year, and it really is an exhaustive job to look for the right JS library for every case, this is my
by elboru 8y ago
I'm a C# developer who has been learning React for the past year, and it really is an exhaustive job to look for the right JS library for every case, this is my process:
1. Facing a code task.
2. Asking myself, should I reinvent the wheel or should I look for a library?
3. Google for libraries solving the task, open at least 5 npm/github tabs.
4. For every tab, I should make sure the library is not too big for my needs/popular/still being maintained/not too many open issues.
-Closing the tabs that didn't pass this step.
5. Taking a look at documentation/examples to determine if it can solve my problem.
-Closing the tabs that didn't pass this step.
6. Testing the library and see if I can make it work.
7. Implement it in my project.
It's a really different environment, and it has its advantages, it's just that Microsoft has spoiled me a little with their out of the box implementations.
- growlist 8y agoAs a dev that's trying to brush up on JS after neglecting it for years, it's really hard to know where to start.