The quickfix window is so small, so I added the "-c only" option to make it the only window that first pops up. Then made it a function so it's easier to call:
```
vgrep() {
rg --vimgrep "$1" | vim -c cb! -c copen -c only -
}
```
Klaus argues that while it is very easy to write unsafe C++ due to language defaults, modern tools and language features, such as
- ranges over loops,
- strong types with concepts over primitives, and
- value semantics over references
provide a safe abstraction over a fast core. He also urges people to use constexpr wherever possible and write consteval tests to catch undefined behaviour at compile-time.
In his opinion, the "People problem" of C++ is that developers are not disciplined enough, or simply don't know any better, as even most books about C++ don't keep up with recent developments and cultural shifts.
The GA144 chip is a 12x12 grid of RISC Stack oriented CPUs with networking hardware between them. Each can be doing something different.
The BitGrid is bit oriented, not bytes or words, which makes if flexible for doing FP8, FP16, or whatever other type of calculation is required. Since everything is clocked at the same rate/step, data flows continuously, without need for queue/dequeue, etc.
Ideally, a chip could be made that's a billion cells. The structure is simple, and uniform. An emulator exists, and that would return the exact same answer (albeit much slower) than a billion cell chip. You could divide up simulation among a network of CPUs to speed it up.
