4 ms·

Bummer. What an unfortunate comment. Many people in the Python GraphQL ecosystem are very aware of how much I pushed that ecosystem forward (in fact, I created

Bummer. What an unfortunate comment. Many people in the Python GraphQL ecosystem are very aware of how much I pushed that ecosystem forward (in fact, I created it!) and actually cheered for the success of Quiver [1]. Probably downloads will speak louder than any words: Graphene has 1/5th of the downloads of Django (~1.2 million per month [2]), all on the spirit of an open community that is governed by many more people than myself. If you want an open alternative to Quiver, you can start by investing your time creating it. But you are not entitled on other people's time doing it for you for free. As people say in the US: "Put your money (or time) where your mouth is". [1] https://news.ycombinator.com/item?id=17568848 https://news.ycombinator.com/item?id=17568848 [2] https://pypistats.org/packages/graphene https://pypistats.org/packages/graphene

srcreigh 5y ago
I have no problems paying for good services. Is quiver still available and supported? When I checked the demo website a few weeks ago it seemed a bit abandoned. [0] We seem to be doing well enough by disabling middleware promise wrapping via middleware manager [1]. Our median graphQL API response times got 2x faster with that config change. However, IIRC we are still seeing around 150 promises in one GraphQL request when I'd like to see around 1. I am interested in quiver for that reason. Anyway, the problem isn't about charging for your work. It's about having a track record of charging for closed source additions to your own open source software platform meanwhile saying wasmer and sibling projects will be free forever as if that's how it's always been with everything else. [0]: https://graphql-quiver.com/benchmarks/ https://graphql-quiver.com/benchmarks/ [1]: https://github.com/graphql-python/graphql-core-legacy/blob/master/graphql/execution/middleware.py#L14-L29 https://github.com/graphql-python/graphql-core-legacy/blob/m...
- syrusakbary 5y ago
  > It's about having a track record of charging for closed source additions to your own open source software platform This is completely false. In fact, it has been rather the opposite. Thanks to Quiver I did improved a lot of things on the open-source GraphQL-core that benefited the whole community. Quiver was built as a completely new product, and to be crystal clear: it never took any open-source bits out of Graphene or GraphQL-core. Basically, anything that was open-source did continue being open-source. That's as true for Graphene as it is for Wasmer. I'm genuinely curious. On which ground you based your allegations?

srcreigh 5y ago

I have no problems paying for good services. Is quiver still available and supported? When I checked the demo website a few weeks ago it seemed a bit abandoned. [0] We seem to be doing well enough by disabling middleware promise wrapping via middleware manager [1]. Our median graphQL API response times got 2x faster with that config change. However, IIRC we are still seeing around 150 promises in one GraphQL request when I'd like to see around 1. I am interested in quiver for that reason. Anyway, the problem isn't about charging for your work. It's about having a track record of charging for closed source additions to your own open source software platform meanwhile saying wasmer and sibling projects will be free forever as if that's how it's always been with everything else. [0]: https://graphql-quiver.com/benchmarks/ https://graphql-quiver.com/benchmarks/ [1]: https://github.com/graphql-python/graphql-core-legacy/blob/master/graphql/execution/middleware.py#L14-L29 https://github.com/graphql-python/graphql-core-legacy/blob/m...

syrusakbary 5y ago
> It's about having a track record of charging for closed source additions to your own open source software platform This is completely false. In fact, it has been rather the opposite. Thanks to Quiver I did improved a lot of things on the open-source GraphQL-core that benefited the whole community. Quiver was built as a completely new product, and to be crystal clear: it never took any open-source bits out of Graphene or GraphQL-core. Basically, anything that was open-source did continue being open-source. That's as true for Graphene as it is for Wasmer. I'm genuinely curious. On which ground you based your allegations?