5 ms·
It was about time. I did some benchmarks few years ago and the results were disgusting compared to native lib, plus why so many dependencies for a simple reques
by craftoman 7y ago
It was about time. I did some benchmarks few years ago and the results were disgusting compared to native lib, plus why so many dependencies for a simple request library? I will never understand why it gained so much publicly, it was worthless since the day one.
- have_faith 7y agoSeems like a disrespectful way of describing someone else's work, regardless of shortcomings.
- craftoman 7y agoYou know how many packages out there are better than request? Now compare all the work those great developers did, gave their souls for what? 50 stars at GitHub? Cmon, let's face the real problem here which is the balance between good code versus popular code. I'm speaking behalf of every great developer out there that spends hundreds of time and his project got faded inconspicuously. I have seen hardcore projects that every tech company could have envied get like 50 dollars of donations and projects that were made in one day, get thousands.
- UnFleshedOne 7y agoThat's just Power Law. Like it or not, I don't think there is a workaround.
- craftoman 7y agoLike judging a book by it's cover or the number of sales. No one said programmers are geniuses, they're just masters of some tools that forge the digital era, nothing more nothing less.
- kaushikt 7y agoThere is no reason to be disrespectful. As a user of Request for the past couple of years, it has made my life absolutely simple. I never had to worry about making HTTP requests and catching all those errors because it did this and a lot lot more. I've worked on several projects and not all of them ever sat down and wondered the benchmarks at a very high scale and the number of dependencies it needed. It's not a criteria for all the projects in the world. I have utmost respect for the maintainers and contributors of Request and so should you.