To me, the coolest is sqlx. It uses macros to do static type checking on plain SQL statements. It verifies types of bound parameters as well as results. It's async, which plays nicely with the leading web frameworks, etc.
LBJ's home office in Texas was preserved, and is still on display as-is to this day. On the couch is a pillow embroidered "This is my ranch, and I do as I damn please!"
The emacs support is great. I use emacs 'racer' and 'lsp' packages full time for development.
There are two popular emacs packages for rust-analyzer: lsp[0] and eglot[1]. lsp (language server protocol) package is the default for racer. Eglot has far more features and is correspondingly resource hungry.
Detailed type information has a super helpful impact on my ability to review Rust code in general. I find reviewing rust code much more productive when I can see what owns a variable, how long it lives, and how it's being used (immutable vs mutable). So yea, lsp or eglot. Super helpful.
Cool. It would be interesting to compare benchmarks the RPC latency under heavy load for pb-jelly compared to other RPC methods.
Rust has such great support for performant zero copy serialization and de-serialization in various formats (bincode, message pack, cbor, bson). Seeing this for protobuf feels very encouraging.
The antibody fits the spike protein like a lock and key. They key might fit other locks in humans with varying degrees of fit, on other cells in the body.
There are two such lock-and-keys on the antibody, the other key fits the immune system cells, that start a cascade that amplifies the immune response.
Even if it is a weak fit for an unintended target, the response can be an issue.
The performance and stability improvements in rust-analyzer over the last six months have been remarkable. Kudos to matklad and the whole team behind this. I'm using it full time now.
It's helpful to have a chance to see hard it is to obtain an increase in Google API rate limits. The documentations suggests one only needs to ask, so this clarification is very much appreciated.
Yea, for the first year of cub scouts with 5 year olds, that's the appropriate kind of activity that combines play, limited strength and skills, and allows you to mix in information about nature, society, arts, science, etc. That said, you also start camping the same year, with your parents, and transition to sharing tents with other kids over then next year or two. By the time kids are 10, they are running the boy scout troop, and the adults should be there just for support and advice. I put it this way: In cub scouts, the adults are at the front of the room. In boy scouts the adults are in the back of the room. In Venture/Explorer scouts, the adults are in the next room.
For cub scout camp directors, the plan must include daily scheduled periods of 'down time' during which scouts can play on open fields or playgrounds. For a four hour/day camp, this might be 30 to 45 min in the middle of the schedule. There's also free time before and after opening and closing ceremonies. The same is generally advised for meetings. Before a meeting, it's best to give them some time to blow off steam before having them sit for any length of time for anything structured. Making things fun is the best first step toward not only engaging them as individuals, but getting them engaged with each other. So yea, essential and well recognized by experienced scout leaders
In June, the Open Markets Institute [0] filed an amicus brief opposing Facebook’s motion to seal records in the case, arguing this matter “greatly implicates the public interest. [1]”
If NSO group develops exploits, why would they have early access?