this is 100% an apple issue.
apple forces people to build on apple hardware.
every FAANG level company/hyperscaler has data centers full of mac minis.
every "ci/cd for ios" which "runs on builds" automagically runs on a apple device in a datacenter.
every other build env can be inside of a reusable docker container cept one. Apple, ios, macos, tvos etc.
I have build entire supply chain "exceptionally flows" to support mac mini iOS building farms to support ios. Ironically their usecase is EXACTLY why they would need and exactly why this is 100% an APPLE issue. APPLE forces this, and APPLE is to blame here.
@mczub I talk to people about discord here and there and you would be surprised how little people actually understand what and "how" discord works and its features. its amazing some of these people use it every day
@cnakazawa I love GQL and Relay. I have went back and forth with alot people smarter then me on this over and over but 1) if you hate relay, you probably just hate GQL 2) there is "no reason" to use GQL without relay. If you do use GQL without relay, you will hit the "why do i hate myself?"
I have a lot of thoughts about GraphQL in general, and I could probably talk about these 2-4 tweets for hours and hours, and have (much to the dismay of @Vjeux) I feel the issue "with graphQL" is rather or not you like Relay or you like Apollo/React Query.
Complexity is definitely not what's wrong with GraphQL. Poor design is. Weak type system (no sum types, no generics, everything-nullable-by-default), incoherent error handling, introspection security liability, subscriptions underspecified, mostly broken CDN & browser caching,
@cnakazawa another "gotcha" with GQL is your thoughts on recursive types. aka 1) input/output objects and 2) types in general should support being recursive. the implementation of this in your GQL server will tell me if people hate who created it hate GQL or not ;o