When you treat your graph like a set of nodes, you miss the point of GraphQL.
...leads to the common impression that building out a GraphQL API is busy work... And moreover, this is true! This way of doing things sells GraphQL short.
...serious GraphQL users like Meta and Netflix have their own entity based frameworks to construct supergraphs.
Building an app or API without a supergraph is like storing your data in files instead of a relational database.
Thanks. A lot of these things ring true in a very practical sense.
GraphQL keeps getting more mature and adding more and more tooling/features/middleware, but we also need to work on de-risking the technology from a more fundamental perspective to get to a rock solid foundation.
Lightning has been around for more than 10 years. Now customers can't reuse those cables / accessories. Though I'm sure plenty will welcome the consolidation as well. So the narrative is good for Apple.
Also the facts show Apple lobbied against usb c in the EU: innovation and patents, phone too thin.
I'm honestly annoyed by this, Lightning is a strictly better connector from a mechanical perspective, and that affects my life 100x more than any theoretical speed improvements
The latching mechanism is simpler, more robust gives better tactile feedback to confirm connection, the port itself lends itself to easier cleaning...
I'm almost certain Apple is moving to USB C not to appease the totally toothless EU, but because it's just gotten cheaper for them at this point. They're making the phone worse to save money.
I feel like the "floating" bits in the center of the ports will break like crazy.
If I put on my game theory/conspiracy cap on, it could be interesting to deliberately make that part of the port extra flimsy so Apple has an excuse (due to public out cry) to remove the port completely and go full wireless, both charging and data.
A world where every life, even a dogs life is different f value.
Can the path to a solution exclude the solution itself.