The article is a nice read, I also agree that they are a contributor to the go ecosystem. That being said, a key issue didn't get mentioned in the article - the

The article is a nice read, I also agree that they are a contributor to the go ecosystem. That being said, a key issue didn't get mentioned in the article - the team is not fully technically competent for the products they are building. A few years ago, I spent weeks evaluating their products, including the graph db and some of their open source libraries. I have to say that you are a brave man if you use some of their stuff in your production system. Good luck to you and your whole team is the only thing I can say. To give you some examples, when I had obvious safety issues raised, quite often I got pushed back with all sorts of excuses, including from Manish himself. That is something more than technical - it is a culture issue from the top. From memory, they even had an angry ex-employee exposing all sorts of bugs, including safety ones, in their products after leaving the company. At some point, they even had their issue section of one of their github repos closed as a response! If you don't know what I am talking about, just check their code committed back between 2017-2019.