Not necessarily so. The history of FTP servers is ridden by bugs with practically no exceptions. At some point some folks decided they finally implement a bug-free implementation and even dared to call it "Very Secure FTPd." Needless to say, it turned out it has bugs, too.
As most of these bugs were related to buffer overflows and similar issues, implementing a new FTP server in a safer language is not such a bad idea, and today's JavaScript is efficient enough to make it a reasonably well-working implementation. I pity the author though for the bugs they encounter and workarounds that will need to be implemented.
Exactly my reasoning. See my comment above for more info.
I'm making the maintenance of this less painful by doing a hacking/debugging session with manufacturers once a month where we hook up many devices and fix issues. After addressing most edge cases fewer are coming up now (despite a relentless stream of new cheaply manufactured devices)
fyi on swoole, this book [1] just came out (I cannot comment on the quality, haven't read yet) which hopefully will help bridge the English documentation gap. I've been using swoole for a couple of years and google-translating my way through the Chinese wiki and git issues/comments/etc.
Swoole (module) is extremely performant in anything networking, including as a websocket server. There are other php-only options (amphp/websocket-server, ratchetphp/Ratchet) but if performance is your need, stick with swoole.
I'm glad Marco finally stepped up to set the HN groupthink tone because you guys have been salivating to defend Apple the past month in every goddamn thread about Epic Games.
Obviously some HN users have defending Apple while others have been denouncing Apple. So much so that I've had to pin moderation comments to the top asking for better discussion than Glory-to-$BigCo vs. Death-to-$BigCo flamewars [1].
But everyone notices and remembers the comments they dislike the most [2], so each side thinks that "HN" is slavishly and perversely on the other side [3]. It would be good to get a little more awareness into this process.
> It would be good to get a little more awareness into this process.
Make upvotes and downvotes public, and do something to reduce the constant flood of throwaway accounts who do nothing more than constant trolling on contentious topics.
Downvotes and upvotes being hidden is the only thing keeping HN from devolving into reddit. Otherwise, people would just agree with whatever had the biggest number instead of (hopefully) applying some critical thinking.
I'm not talking about the quantity, I'm talking about a list of who upvoted and downvoted a specific comment/post.
Also what you've described happens anyway. The fact that a number isn't displayed doesn't really matter when comments are ultimately ordered by score. When someone writes a comment that doesn't adhere to the current groupthink, they get downvoted. When people are downvoted too much they delete their comments, stop commenting, or through pavlovian reinforcement change their opinions until they get positive points.
There's a difference between defending Apple vs Epic, and defending Apple vs itself - Epic acted horribly. It was much easier to defend Apple's position than Epic's, even though I hope that Epic's revolt will push Apple to change their App Store policies.
It's funny; coming from the other side, I mostly see people opining confidently that Obviously the Supreme Court Will Cap Apple's Fees at 1.5% or the EU Will Most Certainly Break Apple Up etc.
