HN user
Context AI published a statement https://context.ai/security-update
Last month, we identified and stopped a security incident involving unauthorized access to our AWS environment.
Today, based on information provided by Vercel and some additional internal investigation, we learned that, during the incident last month, the unauthorized actor also likely compromised OAuth tokens for some of our consumer users.
Be careful what you wish for
This is basically what most cloud platforms provide. Cloudflare has some of the most high level components/building blocks imo.
I appreciate the effective use of diagrams. The boundaries are separated really nicely.
But grpc isn't limited to go. Criticizing gprc, as a whole, for the http library used with go isn't valid. However, it's fair to take issue with the choice of http library used by the most popular go codegen tool.
In that case, I would imagine you would struggle with any clients generated via an IDL. The same "issue" occurs with openapi/swagger generated clients.
If you're not working on whatever is responsible for generating the code, you're not supposed to have to look under the hood. The whole purpose is to abstract away the implementation details, it's contract driven development. If you find yourself frequently needing to read the underlying code to figure out what's going on, the problem isn't with the tool, it's elsewhere.
Originally, I was going to complain that this is more of a critique of the grpc ecosystem rather than protocol.
IMO, readability of generated code, is largely a non concern for the vast majority use cases. Additionally, if anything it's more so a criticism of the codegen tool. Same with the complaints around the http server used with go.
However, I totally agree with criticisms of the enum naming conventions. It's an abomination and super leaky. Made worse by the fact it's part of the official(?) style guide https://protobuf.dev/programming-guides/style/#enums
I don't see how this is different from when people trade based on what Warren Buffet does.
this is interesting. have you leveraged gpt3 for this previously? do you expect any advantages with the updated model?