When you're working at a real systems level c is so much easier to get up and running with. These are hard problems and getting something just to a working stage can be a real challenge. C is also really simple in comparison to those mentioned, and there are a lot of people that enjoy working with c/asm.
Zig is not stable and will not be for sometime. It has a few quirks that bother me, but I look forward to using it more seriously once they release 1.0.
Rust is a different style of programming, that's not a bad thing, but you can't fault someone for not liking it. I think it's great that a lot of people really like rust, that's awesome, but it's not perfect. It doesn't help that there's a lot of condescension towards other languages coming from rust zealots.
Go's GC makes it a non starter in certain domains.
C 'package management' isn't that difficult once you understand the tooling, and there's a lot of freedom that you come to appreciate when you're writing a driver, bootloader, porting to a custom/exotic os, etc. clangd
works fantastically so it's not lacking lsp goodies.
Real systems programming is a much smaller field than other disciplines so it does not surprise me that programmers as a whole don't understand what makes c great.
Naw, 5 + 1 = 6, 6 is divisible by 3, so 51 is divisible by 3.
Worked for jesus.
Snoop 'nothing but love and respect for donald trump' Dogg? GTFO.
What if I prefer this?
#define CURLYOPENRIGHTCLOSEDLEFTBRACKET {
#define CURLYOPENLEFTCLOSEDRIGHTBRACKET }
#define CURVYOPENRIGHTCLOSEDLEFTBRACKET (
#define CURVYOPENLEFTCLOSEDRIGHTBRACKET )
#define PERIODWITHPERIODONTOP :
#define COMMAWITHPERIODONTOP ;
int main CURVYOPENRIGHTCLOSEDLEFTBRACKET CURVYOPENLEFTCLOSEDRIGHTBRACKET CURLYOPENRIGHTCLOSEDLEFTBRACKET
if CURVYOPENRIGHTCLOSEDLEFTBRACKET 1 CURVYOPENLEFTCLOSEDRIGHTBRACKET CURLYOPENRIGHTCLOSEDLEFTBRACKET
asm volatile CURVYOPENRIGHTCLOSEDLEFTBRACKET
"mov $1, %%rax\n"
"mov $1, %%rdi\n"
"lea message(%%rip), %%rsi\n"
"mov $4, %%edx\n"
"syscall\n"
PERIODWITHPERIODONTOP
PERIODWITHPERIODONTOP
PERIODWITHPERIODONTOP "%rax", "%rdi", "%rsi", "%rdx"
CURVYOPENLEFTCLOSEDRIGHTBRACKET COMMAWITHPERIODONTOP
CURLYOPENLEFTCLOSEDRIGHTBRACKET
return 0 COMMAWITHPERIODONTOP
CURLYOPENLEFTCLOSEDRIGHTBRACKET
asm CURVYOPENRIGHTCLOSEDLEFTBRACKET ".section .data\n"
"message: .ascii \"wut\\n\"\n"
".section .text\n" CURVYOPENLEFTCLOSEDRIGHTBRACKET COMMAWITHPERIODONTOP
Strategically speaking liberal politicians are backed into a corner and only have two real options:
-
Seize control preemptively, promoting conservative conspiracy to prophecy, and likely inciting CW2.
-
Hand over full control come January and hope they continue to maintain some privilege under a new regime.
They're already in check, but more concerned with soliciting large donations and collecting hot stick tips.
On one hand, I can think of good reasons not to disclose HRT or any other personal medical information to your employer, 'district surgeon' or not.
On the other hand, ACAB, get fukt.
1 Timothy 2:11-12: “A woman should learn in quietness and full submission. I do not permit a woman to teach or to have authority over a man; she must be silent.”
most significantly, it could hurt our quarterly revenue, which is the worst tragedy imaginable.
Here lies the root of the issue, we've simply reached the logical conclusion of a greed based economic system.