I can't figure out why this font is better than DejaVu Mono, or Monaco (mac). They all look basically the same to me. I actually would love someone to explain what the difference/improvement is, in other parts of life I know subtle changes add up.
Most Linux CVEs are memory corruption bugs. Previously I argued that we should compile C to be memory-safe rather than translating all C to Rust, to avoid introducing logic bugs.
Here, I argue that several parts of the kernel can also be compiled in a memory-safe way.
Yeah, but long term it will increase GDP due to the UK being able to have better (fewer) regulations than those allowed by the EU. It does require Parliament getting it together.
> First, like others mentioned, you'll have N+1 problems for nested lists. That is, if we call comments() on each post and author() on each comment, we absolutely don't want to have one individual call per nested object. In GraphQL, with the data loader pattern, this is just 3 calls.
Why is that a problem? As far as I can tell, those calls are all done on the server, where they're cheap normal function calls, and the results are all sent back with 1 roundtrip; because of the pipelining.
Super cool work!! How much of a limitation is it to have the robot be basically 3D-printable? Though I can see it's basically required for making it buildable by others.
The easiest thing to do is probably use A* to find the solution, then imitation learning on the NN to learn it. (The immediate feedback gets rid of the vanishing/exploding gradients problem).
> After further investigation and communication. This is not a bug. The threat actor group in question installed headless chrome and simply computed the proof of work. I'm just going to submit a default rule that blocks huawei.