45 karma · joined December 5, 2022
What you want is the idea of bootstrapping. Write your compiler in C, then as your language specification is developed enough, dogfood your own compiler. Write your compiler in your new language, then compile itself. This is called bootstrapping and is how many languages are developed. Once you are fully bootstrapped you can drop C altogether.
https://gcc.gnu.org/wiki/DontUseInlineAsm
https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html
I don't use Rust so I can't comment on it but it also has compiler intrinsics + a memory safety model. It's compiler is really dog slow last time I used it so I hope that has improved but nobody is really killing C any time soon, even if there's enthusiasm for memory safety. Sooner or later you have to delve down into the depths of Narnia and you may as well get comfortable dealing with memory.
My likely favorite combination is Python + C (for the speed stuff) + Intrinsics (for the really speed stuff).
It shows experience with people and ability to read between the lines.
I can only infer what happened but they really didn't want me to be without a regular phone line so I determined that was their legal weakness. The only way companies that large move like that is if something threatens their status with the local government. A call from a resident saying the company wouldn't install a phone line is a big no-no in my understanding.
One of my favorite shows of all time. Excited to watch anything that's even remotely related to this.
The problem seems to be whether or not the content was generated via language modeling or via direct references. When it crosses into language modeling it is just making stuff up on the fly. This sometimes works for programming, but for specific things that connect to the real world it can be phenomenally wrong.