Wednesday 15 August 2018

The "uws" NPM deprecation response

Why hello there,I've heard through the grapevine there's been some lively talks and speculation regarding the recent NPM deprecation of "uws" module. I've somewhat read the three threads here on reddit:https://ift.tt/2vJmbBs Q & A:Why was the NPM module deprecated?I've felt for a long time that the NPM registry does not respect my decisions to control the project in ways I want to. In my view NPM should merely act as a hosting service and host my verbatim content. NPM is not as liberal as I would like to. I don't care for third parties who enforce decisions in areas where they should have no say. NPM should host things and let the market control itself. Also, their terms of use is an American nightmare: Unlimited, eternal, indemnification liabilities + inability to ever delete, modify or republish = unacceptable.What happened to the project?Nothing. Nothing at all happened. It is still used and last version is available on NPM just like before. It is marked "deprecated" but that doesn't mean you can't use it until next version is released. I never deprecated "uws". I deprecated all versions currently on NPM because that's the strongest hint I can leave there before deleting my account.Why are you such a cunt-bastard-moron chicken-fucker sabotaging prolapsed anus hole?Thanks for the nice words. So I realize that my patch update affected more people than I anticipated. My strategy was to post a "broken" patch version with a sorti message so that the 10 or so people who are on latest got the message and spread it. I kind of misjudged the number of people sitting on latest, obviously. But hey - the strategy worked and people got the message. Libraries.io statistics are obviously not that reliable!He's a dickhead cunt face asshole elitist fuck bag.I would argue you're wrong. Maybe it's your attitude. Why would you even write such a thing? Obviously there's some anger problems here. There are 151 commits from third parties in the repo which I have merged with positive feedback. For every merged PR there are 10 unmerged ones though, so generally negativity is abundant and frankly most PRs are really really really bad and completely incoherent. If you want a nice response then write good code, provide good issue reports and behave. I don't merge PRs I don't agree with and I will instantly close any CMake PR, just like I've done some 100 times already (with increasing neglect).When will next version be ready?When I feel it's ready. If you want a time estimate or come with opinions you can sponsor the project. I don't write code for you, I write it for me and my sponsors. Unless you're saying bring back slavery, don't take the freedom to demand anything for free. You did not pay for this, thus you have no say whatsoever. Saying "thanks" in a mail does not constitute an actual thank you.Why did you nuke the Node.js repo?I didn't. It is hosted as a fork at many places on the internet and I have a copy on my computer. The reason I removed the repo from uNetworking is because I am in a transition phase where it will be rewritten and majorly improved for next major release. You need to nuke your code from time to time you see. Keeping old garbage code is not what I call evolution.Why are you writing open source code?People in open source are very quick at assuming every one else thinks exactly the same. I don't. This "community" and "maintainer" lingo doesn't apply here. Reddit user "BenjiSponge" did an excellent analysis of how I work and think. I'm, unlike 90% of all GitHub users not a socialist. I don't write open source because I believe the code belongs to the public or any of those communist ideas. I write open source for two reasons: money and money. Respect that, don't project your utopian views on my projects and try and bend it around your foot.Why should I even use uws?You tell me. It's not my issue to solve. If it works for you, good. I would say at least rather use "uws" than some shitty "fork" of it. I've seen some forks before and they all end up the same: unmaintained, stagnated & left behind. Mainly because those who believe they can fork it has no experience at all in the project and no vision for it. I honestly don't get how people rather swap to some third party clone of some 4 month old version than just use the original. But hey, I don't mind. You're not paying me.Where can I get new versions of uws?New versions will most probably be released as tags on GitHub repo uNetworking/uWebSockets-node. What is currently on NPM is not in any way any less usable than before the deprecation though. With releases hosted on GitHub instead of on the NPM registry I get the control of things I want, and you get to easily install versions with the NPM client by specifying the repo and version tag (will be made clear when time is near)./ Alex

Submitted August 15, 2018 at 07:16PM by FeistySail

No comments:

Post a Comment