I'm working on a PEG-based Turing complete language. It is self-hosted, generates standalone/embedable C, is reasonably small, and comes with a fully-featured REPL. It has only a single keyword: "macro". Feel free to reach out if interested.
Getting rear-ended is almost always the other driver's fault, but 7 years ago I was involved in a serious accident (minor injuries, both cars totaled) when the driver in the fast lane decided to pull over and pick up a hitchhiker. Crossed over two lanes, hard on the brakes, and I had no chance to even get off the gas.
The responsibility was 100% his because of "an unsafe lane change".
Yup, this is the primary case where the rear vehicle isn't at fault. You change lanes into a lane that's moving faster and get hit, you were wrong even if they hit you from behind.
If it can be proven. 25 years ago a scam was where someone would suddenly change lanes to be rear ended like that, then claim "back pain" and sue for a lot of $$$. I don't know how common it was, but when there are not witnesses the courts tend to side with the person being rear ended.
Well, maybe. I for one _absolutely_ didn't participate b.c. I didn't want my DNA and personally identifying information owned by any company. I can't imagine that there aren't many others like me.
I would, however, love to send my DNA to a company if they could provide the results without knowing any information about me whatsoever. For instance: I would be more than willing to buy the kit with cash and send it back with a burner email. Has anyone heard of such a service?
But then, without all that extra data, they would actually have to do some dna testing, rather than than determining your likely background heuristically.
I read somewhere a while ago that the FBI gets free access to the data, which was enough reason for me. This is just icing on the cake. Though more than likely a few of my relatives sent it there already, so not that it matters anyway.
There is a reason Pootin, and some other world leaders, have a black case carried behind them by a member of security team. This is to collect poo so no genetic information falls into the vials of the enemy.
I can highly recommend libtcc (https://github.com/TinyCC/tinycc.git) for this kind of thing. I recently ported the code developed in linux on an ARM chromebook to a generic windows box in 20 minutes.
Not exactly a diet tip, but first thing every day (after stretching) I drink a large glass of water (16oz), drink another large glass with a tablespoon or so of psyllium husk, then another large glass of water. Then whatever breakfast I feel like. Psyllium is cheap, safe, and readily available (and most of us should be eating more fiber, right?).
I've had great success with a fourth way: my project language compiles to C, which is loaded at runtime with libtcc (specifically: git://repo.or.cz/tinycc). I've gone down the .so/.dll route a few times in the past, but I can safely say: never again. libtcc has the advantages of a jit (native C speed), but with an elegant API and laudable portability.
One could use it to test (embedded) code targetting RISC-V, without needing to use hardware.
Unit tests is the easiest, since they preferably do no I/O. But also integration test by providing an I/O implementation (using a Hardware Abstraction Layer), and driving I/O from the tests.
Such testing is easier to do when one has C access to the simulator, and not having to implement the I/O via some virtual device shuffling bytes etc.
And since its just a C header/library, on can just distribute, include and build the simulator alone with the project/tests. As opposed to relying on the user having qemu (or similar) installed.
I will consider using it for emlearn (a Machine Learning Library for microcontrollers).
This is a full system simulator with an emulated RISC-V CPU in under a 1000 lines of clean C, in two files, so you can include it basically any program (STB style FTW).
