ejona86

7 ms·

1.
by ejona86 2y ago
If you're already a password manager user, then it sounds like your gripe is "my password manager doesn't support passkeys." That seems either a short-term issue that would be resolved in time, or you need to find a more
2.
by ejona86 2y ago
"Resident keys" is the solution, not the issue. With U2F it was hard to track which sites used the key. If I wanted to move to a different physical key, what sites should I update to not need to worry about arbitrary account recov
3.
by ejona86 2y ago
> ... CP/M for the in-development Vector 4. Switching would potentially mean redesigning the next line of machines. The Vector 4 and 4-S did receive MS-DOS 2.0 support at some point. I have a working Vector 4 with MS-DOS, and this f
4.
by ejona86 3y ago
Size-optimized, RAM-only mods. Sounds interesting...
5.
by ejona86 4y ago
Not just you. It can give no results and partial results, which is sometimes fixed on a re-query. But it also is just poor for code. I think it wants to find full words, so searching for substrings generally results in too few matches. That
6.
by ejona86 8y ago
It is true that gRPC tends to implicitly imply Protocol Buffers. It's the only format that is worked on directly by the gRPC team. However, C#/C++ Bond, C++ FlatBuffers, and Java Avro have some level of code generation support for
7.
by ejona86 9y ago
The thing that went unnoticed with that issue is that grpc-go didn't have an option to manually increase the window size. Both the Java and C implementations had the option much earlier; I see a commit adding it in Java in March 2015.
8.
by ejona86 12y ago
HTTP/2 has the concept of streams. Each stream is independent, but within a stream data and headers are ordered. Each HTTP request would be on a new stream. gRPC maps calls to streams so calls can proceed at different rates, but you st
9.
by ejona86 12y ago
HTTP/2 is quite featureful and provides most of the advanced needs that gRPC has; HTTP/2 is pretty similar to what we would make ourselves if gRPC used TCP directly. Using HTTP/2 though also allows fitting into the wider web
10.
by ejona86 12y ago
gRPC actually still has to calculate the length of a message before transferring it.
11.
by ejona86 12y ago
And using HTTP/2 directly allows using HTTP/2-based load balancers and reverse proxies, which is a huge bonus.
12.
by ejona86 12y ago
When people might be comparing it to REST with JSON, it is fast. gRPC can be used with flatbuffers and similar. The experience has been targeting protobufs, but at its core it just expects a serialized message. Other formats can be made to
13.
by ejona86 12y ago
Immutability is still there. You get to choose whether you want it or not. For when you actually want a nullable field, I think the idea is that it is easy to have a wrapper message (just like boxing in languages). Such wrappers could even
14.
by ejona86 12y ago
The Java examples are in the examples folder: https://github.com/grpc/grpc-java/tree/master/examples/src/m... The examples folder references a tutorial at https://github.com/grp
15.
by ejona86 12y ago
It varies based on language: some languages use async callbacks, some use futures/promises, some block and require threads, and some support multiple forms. The intent is that programmers in that language would handle concurrency howev