gRPC and GraphQL have the same problem of using HTTP as a transport layer rather than as the API medium, plus the tooling is specific to their framework. Ideally I’d like to define operations that get compiled to separate HTTP endpoints
Anybody aware of existing tooling like this that I’m just not finding? I want something that compiles down to OpenAPI but isn’t so HTTP oriented in its definition https://t.co/2nptJ3Hq7A
JSON-RPC ends up moving routing into the payload, meaning the same HTTP endpoint gets invoked and you have to re-implement monitoring all over again at a lower layer, plus the project looks dead
People don’t choose to be LGBTQI+, but businesses sure seem to choose when to support it when it cushions the bottom line and doesn’t cause bad PR. Pride is a protest 🏳️🌈
Developers of iOS apps please come to a consensus on how contextual menus should behave. Do I hold and slide to release or do I hold, release, and tap. Otherwise sending ❤️ accidentally to bad news is going to continue.
How is @audible_com zeroing out your credits you’ve accrued with your monthly fees when you cancel your subscription not considered shady? Thanks for nothing 😒
I always said I didn’t want to be treated differently because I’m gay.
But last night, I had a conversation that made me realise it’s important to acknowledge that what I’ve been through *has* made me different.
It helped to talk about it, and it’s helped to write about it.