Well, it's my framework. 🤷♂️ Hoping to hear in the comments what others use!
I go straight for the commits list, it's the best marketing material! But there are exceptions, fetch-mock-jest is something I'm using in my tests that's a small wrapper around fetch. Last commit 4 years ago, still works flawlessly. 😅
Taking dependencies is like committing to a relationship. There are always new potential partners. But at the same time, nobody wants an unstable relationship...
I didn't know the 3-Ms framework and it's interesting to make sure we make a balanced decision
That's a great way to put it. :) 3M is something I've come up with, but I'm sure other people have their tried & true ways of picking technologies and I hope I'll hear about those in the comments!
Very interesting framework! It was new to me. And I loved the personal stories :)
I find that the best indicator is the frequency of commits. If the last commit to master was 2-3 years ago - that's a huge red flag.
And thanks for the mention!
Well, it's my framework. 🤷♂️ Hoping to hear in the comments what others use!
I go straight for the commits list, it's the best marketing material! But there are exceptions, fetch-mock-jest is something I'm using in my tests that's a small wrapper around fetch. Last commit 4 years ago, still works flawlessly. 😅
Great post, Anton!
Yeah, good call about small libraries. Sometimes a package can solve a very specific need, with minimal changes required.
Exactly! Worst case, you fork it and make the changes you need.
Thanks for the mention, Akos!
Taking dependencies is like committing to a relationship. There are always new potential partners. But at the same time, nobody wants an unstable relationship...
I didn't know the 3-Ms framework and it's interesting to make sure we make a balanced decision
That's a great way to put it. :) 3M is something I've come up with, but I'm sure other people have their tried & true ways of picking technologies and I hope I'll hear about those in the comments!
Love your post!