People often ask me how I maintain +600 modules (for free usually). I usually reply "because most are small and done". Node 10 deprecates an API used by 141 of them, 176 if you include tests/examples. This is *after* spending time getting a bunch other of my modules updated.
-
Show this thread
-
The big irony being I (along with
@feross) was the one opening the original issue pointing out the problems with the API. Had I known it would lead to the deprecation I honestly would never have reported it, the impact is just too massive on module developers.1 reply 4 retweets 33 likesShow this thread -
Spending time updating this takes free time away, contracting time away, time working on new distributed systems away. It's a massive task for me. So massive I probably wont bother. Simply too expensive.
3 replies 2 retweets 25 likesShow this thread -
It's a tricky issue. How do you deal with deprecating API that are massively used? Well my answer is always "this is exactly why a big core is problematic" and why userland should always win. If this was a userland API, you'd simply major bump it and move on.
3 replies 5 retweets 52 likesShow this thread -
Core does not have this privilege. It's a massive peer dependency. You are simply out of luck to any kind of this change IMO. You can do outreach to get important things updated (this has already happened btw), but the API can never go away.
6 replies 0 retweets 15 likesShow this thread
Node would do well to adopt the Linux mantra of "never break userspace".
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.