Case in point, I bought a bunch of metric bolts and nuts at Amazon, and they wouldn't screw onto each other. They would get to some random point and the nuts would stop turning. Sometimes it was half an inch up,

There's your problem!

But seriously, this doesn't generally match my experience. I haven't bought nuts and bolts there because they're cheaply and readily available locally, though China is obviously more than capable of making screws at scale. So much consumer electronics is made there, they can certainly do that.

It is strictly a market place, so YMMV, but honestly... it's pretty good.

If I respond in a NON LEFTEST way, I usually get banned for 1-2 days.

Oh they only ban for 1-2 days for really racist posts?

They are NOT a free speech place.

Free speech does not mean any particular person is obligated to give you a platform for racism. If you want to be racist in company head on over to X or Truth Social.

I was there for the beginning and in the end they went way overboard on the SJW.

Translation: people did not appreciate my racist comments.

but if you don't know what the compiler is going to do with your code you should have used another language.

I would say this rules out about 99.99% of C programmers from using C then.

The problem is that the areas where the evangelists want Rust to save the world,

Eh? I'm just making an argument about what the compiler is doing.

you're usually going to be doing that.

This is exceptionally doubtful.

It's a mirage.

It is not. Even if we wildly overestimate the amount of raw pointer fuckage you actually need to, say, 50% of kernel code you've still got the compiler eliminating certain bug classes in the remaining 50% of code. That is no mirage.

Most of the time when you can have all the protections, why are you even trying to use a compiled language?

At this point I don't know if you're asking a rhetorical question or if you genuinely don't know why one would want to use a compiled language.

Keep telling yourself that

It's very easy to keep doing because you keep flinging poo without saying anything of substance.

Seriously, Rust and C share an application domain,

Yes.

And Rust is complex.

Yes, and? Never said it wasn't. If you want a simple language, use Brainfuck or Unlambda. Few languages are simpler than those. When you actually think and understand why they are bad languages for programming, you will just get an inkling of why having a simple language can simply push complexity onto the programmer.

Incidentally, I am not a "C fanatic"

Flinging invective, saying nothing of substance? Yeah you're a fanatic.

I think C fanatics are possibly even worse than Rust fanatics.

No debate, no argument, just flinging poo and ignoring the last 70 years of computer science development.

I note you didn't actually address a single point. It's because you know you can't and know you are wrong.

I was going to use Google as an example of how it should work. Chrome supports open standards, and incompatibilities are minimal because if Chrome doesn't conform to the spec it's treated as a bug and fixed. When Google wants to add new features, they go through the process of getting them added as open standards. Sometimes they fail and have to be abandoned, and Google accepts it, e.g. the pseudo-anonymous ad impression reporting tech they developed.

Google actually has an open standard for spreadsheet programming using Javascript, which it's a shame nobody else uses because it's the last big hurdle to migrating away from Excel for a lot of people.

Well, you'd be wrong, but don't let it change your opinion.

I like C++, it's fun. Nice combination of being able to do whateverthefuck you want but also you can program the compiler. C has the former but not the latter, and as a programmer I like to program rather than be weirdly precious about not programing the compiler.

I love AWK. It's just so good at what it does, and amazingly underrated.

BASH is my homeboy.

sed, because sometimes life is too easy

Python and Java are... fine. I like programming in general and they scratch those itches but I don't love the languages.

Machine code a fun once but once is enough.

I quite like PIC ASM on tiny tiny PICs. Don't love doing bigger things in it really.

Shader graphs are just fun.

TCL is the bananas platonic ideal of a stringly typed language and I enjoy it exists. I had some fun programing in it once, but I would not like to do it a lot. It's sort of fun just for being strange and alien but masquerading as a more normal language.

RPN languages (PS, Forth) just never gelled with how I work, but I have had fun with postscript in the past.

MATLAB is a bit aggravating and Octave fixes some of the more egregiously annoying things about it.

Oh yeah and scripting complex actions etc in BOOM compatible engines is let us say, barrels of fun.

But C? I love the language for what it is, an appreciate the artistry of it. But for fun of programming? It feels like being stuck locked out of a workshop with all the good tool in.

If Rust is too complex then so is C.

C pushes ALL of the complexity onto the programmer, whereas more recent languages get the computer to do things it's good at.

It also does not, as Linus has pointed out, prevent logic errors.

That's not wrong, it's also not right either. For example, C has no way of distinguishing between a pointer to an array, a pointer to a single datum and a pointer to an object which might not exist (i.e.one that can hold NULL), and of course nothing about the ownership of the pointee. No covering all the cases is a logic error in C, and one the language provides no assistance with.

In C++ and Rust you can distinguish between those cases, which makes not writing logic errors easier (rust goes further on the ownership side).

There are all sorts of things in both languages which allow you to design your code so that certain logic errors are almost impossible by construction. You still have to design it that way, so the language doesn't per-se "prevent it", but allows you to use the language to prevent it. C does not give you enough control to do such things.

This has been the case for a very, very long time already. Corporations have been self censoring forever. You can find maps that are decades old which show Taiwan as part of China, for example.

You would expect nothing less. The far more important issue is people relying on AI as a source of information about these things. People need to learn to always question AI and verify its claims.

On the other hand, C does exactly what you tell it to do.

Not exactly. It does what the compiler, through blind, fast, accurate and utterly mechanically stupid application of the rules of the standard believes you have told it. The standard has scope to allow for demons to fly from your nose and the compiler will oblige you in that if you accidentally ask it to.

Rust always feels like a constant argument with the compiler (linter really?) where it keeps going 'I understand what you are trying to but am not going to do it'

Well not really because you're saying "I want you to do X and prove Y", but the compiler is telling you it cannot prove "Y" if you do "X". But you're asking it to prove Y. So it's doing exactly what you asked (trying to prove Y).

If you don't want it to prove Y than you can always just temporarily switch off the prover (i.e. borrow checker[*]) and fuck around with dereferencing raw pointers to your heart's content in an unsafe block.

[*]Hey rustaceans no one cares about your language specific terminological pedantry when discussing things which include, but are not limited to rust.

If you have fun programming in Rust, you will have fun programming in C.

Programming in C is a bit of a slog, frankly. You have to do every. little. thing. by. hand, even though there's a perfectly good computer sitting right there you could (in principle) use to automate away tedious stuff.

They need a self cleaning system like those public bathrooms where the inside is hosed down between users, and anyone who fails to exit promptly is washed out.

You certainly can write pixels directly into a bitmap on Windows. I suggest using SDL to make your life easier.

I prefer 6502 myself, but the Z80 has some interesting features. The pseudo-DMA mode, essentially an optimized copy loop, is nice. Quite a few games back in the day used it, notably Ghosts and Goblins on the ZX Spectrum which redraws the entire screen with it every frame. It's a relatively easy to integrate chip, and the port feature allows for a clean memory map and low cost/complexity peripherals.

RISC-V is appearing in more and more microcontrollers from Chinese manufacturers, as they seek to move away from dependence on any Western tech. It's still got some way to go to catch up with ARM in performance SoCs, but for low cost microcontrollers it's pretty much on a par now.