Re:Request Node lib used by 48k modules is now deprecated
by DougBTX on Tuesday February 18, 2020 @12:34PM
(#22357965)
> However, the fact that he got "bored" with this solution
That's a horrible mischaracterisation. There's a clear ecosystem-wide shift to async/await instead of nested callbacks, putting a project that depends heavily on callbacks into maintenance mode rather than releasing a new, entirely incompatible version that uses async/await is completely reasonable.
Also worth pointing out is that the same person who posted the maintenance mode announcement also released a request library that does use async/await: https://github.com/mikeal/bent
Re:Request Node lib used by 48k modules is now deprecated
by BenoitEssiambre on Tuesday February 18, 2020 @12:26PM
(#22357833)
>It doesn't have Promise support
That's a feature. https://medium.com/@b.essiambre/continuation-passing-style-p...
Re:Request Node lib used by 48k modules is now deprecated
by hombre_fatal on Tuesday February 18, 2020 @12:34PM
(#22357966)
While this isn't really the place to discuss this, that your most complex example is a simple waterfall of three nested async functions doesn't do much to sell the superiority. Start mixing in conditional async calls with downstream async branching. And look at the Promise-based solutions to async.js (https://caolan.github.io/async/v3/), a library nobody misses. Still not sure if your blog post is a joke or not though, frankly. If it's a serious post, then it seems troll-y to inject such a fringe opinion any time someone casually mentions promises being good.
Re:Request Node lib used by 48k modules is now deprecated
by mekster on Tuesday February 18, 2020 @04:48PM
(#22360747)
What's wrong with,
https://github.com/request/request-promise-native
request is very simple and straightforward library that solves a very common issue.
Deprecating it causes a lot of work for every project out there. Either using request directly or indirectly.
I have a lot of respect for the maintainer, and he can choose to do whatever he wants with this module. That's his privilege.
However, the fact that he got "bored" with this solution, doesn't mean he needs to deprecate it. He can just stop working on it, and give ownership to someone else.
If it had a security issue and he is not going to ever update it, then that would deserve the deprecation so people should be warned.