I said some SFUs development is slow and API difficult to understand. Today they come to my GitHub and said "This is a very disrespectful post. It's just that you suck. Bye."
I want to know that if I was wrong. What's a proper way to compare open source software and do reviews?
https://github.com/MixinNetwork/kraken/issues/4
And I have an emotional response https://vec.io/posts/reviews-of-open-source-software
On your main point, though. I think it's a bit disingenuous for you to say you were just reviewing open source code when your blog post is written more in the style of exploring alternatives and pitching your own solution, but I genuinely do not think you were anywhere close to disrespectful in that post. To be honest, this seems to me like a freak incident way outside the norm. Lots of major companies post about how they explored alternatives or decided to roll their own thing; almost nobody thinks that that's equivalent to panning the alternatives they didn't choose. You've just got to take it on the chin and move on.
As another aside, regardless of how emotional you were, the last paragraph of your new post is rude and unprofessional.
I understand for someone like you, an core engineer of
the famous mediasoup, you are able to make an audio only
SFU from scratch in under 15 minutes, good job.
...
At least could you please make an working example like
the one in Kraken readme, in 15 minutes, without your
awesome but too complicated client library?
And the reply in full was: No, I won't waste my time with people like you. Sorry,
nothing personal. It's just that you suck. Bye.
The "This is a very disrespectful post" part is from another comment altogether.Tempest in a teacup. Flagged.
To your broader point about reviewing libraries; it is an interesting area. I feel that a lot of people (myself included) will assess a library based on an odd combination of heuristics; last commit, timely issue response; thorough documentation etc. Everyone has different priorities. I do wonder if there is value in bringing together reviews or real-world-use feedback in a single place. But you'll need to bring asbestos gloves.
The other person's response 'that you suck' is unprofessional and immature.
If that happened to me I would be inclined to fork and refactor their entire library.
There's no right way, you could praise the hell out of something and conclude that you wanted to write your own just to gain the experience, and someone will still call you an idiot for re-inventing the wheel or find something to complain about.
You simply can't make everyone happy. Don't try. If someone sees value in your work, let them in, if they want to cry about it, ignore them. Life's too short to deal with twats.
Step 2: Move on...