talk

Maybe it's isolated to me and my work here on this repo: https://github.com/coralproject/talk I agree that Relay CAN be simple, but it isn't for what we do. Have a look at this ReplyListContainer and its nested Relay logic. I didn't originally write this, but I can see what they were trying to do and how Relay made it difficult for them. Your thoughts are welcome, I won't judge you for being critical of our code and welcome any other Relay dev's opinions. https://github.com/coralproject/talk/blob/develop/client/src...

The Coral Project [0] (commenting platform used on Washington Post, New York Times, The Verge) uses an Apache 2.0 license [1]. Which doesn't seem to have prevented it from raking in big SaaS customers. A lot of people worry about copy-cat services, but it's kind of rare that someone will be able to compete with you as the original in hosting your own service as well as you can. Especially when you consider support and maintenance requirements of a new product you aren't personally developing. I could see copy-cat services being more of an issue in the late stage of a product though? When everyone knows lots about how to stand it up and use it? [0] https://coralproject.net/ [1] https://github.com/coralproject/talk/blob/develop/LICENSE