Which part of what I said is too binary?

If that happens, you just have to look elsewhere. It can't be trusted. (To be fair, Wikipedia has the same limitation).

What does that even mean?

What kind of schema do you have in which deleting a single entry ends up deleting license keys for 2000 customers? That makes no sense?

That was your prompt, was it? And it just worked? What happened to the other 2000 customers?

Amazing that your entire post sounds nonsensical. You should stop making things up.

Yeah. Here's an example chat with citations, so you can get a feel for what it's like. Bing.com/chat is also worth checking out imo, since it gives better results than Google.

Arrogant programmers throw a tantrum and blame. Skill is an orthogonal trait to arrogance.

Good programmers ask:

1) How did I make that mistake?
2) How can I avoid making the same mistake in the future?
3) Did I make a similar mistake anywhere else (go verify)?

If you do that, you can write secure code in C. If you don't, then you can't write secure code in any language (because memory errors are not the only errors).

My biggest use is as a search engine. Sometimes I'll just use the AI answer Google automatically posts in the search results, or sometimes I'll ask ChatGPT specifically. I don't rely on the answer, I click on the link citations provided, which are sometimes good, sometimes bad. Google AI is still garbage tier, but it does provide link references.

My second biggest use is to generate art. Flowers love you. Time flies like an arrow.

If you use AI as a search engine that's fine, but it's a starting place. A kernel developer needs to have a skill to read documentation for the functions being used, and if that isn't enough to read the actual code. Don't trust AI (or search engines), make sure you understand the code.

This is utterly false. X was designed in the 1980s at MIT. Is it perfect? No, but it does the job.

Wayland was built by Kristian Hogsberg, who definitely did not go to MIT, and has the design skills of a typical RedHat employee.

Good programmers say, "How can I avoid making that mistake in the future? Did I make a similar mistake anywhere else?"

Arrogant programmers get upset. Arrogance is orthogonal to skill (but eventually limits it).

It gets flagged as a warning by most compilers. In GCC, don't disable -Wno-parentheses

Apparently people are actually connecting to Google via ipv6. Maybe those are all mobile users.

As for my ISP, it doesn't even assign me an IPv6 address. I have to use a proxy or something if I want to do that.

Linus doesn't want an apology. He's not upset with Overstreet because Overstreet insulted him, he's upset with Overstreet because Overstreet wrote bad code (or in this case, can't figure out how a merge window works).

All Overstreet needs to do is figure out how a merge window works. He doesn't need to write a perfect apology.

C is a great language for kernel development. It is elegant, in that it serves its purpose well and efficiently. If you know what you are doing, you can write clean, brief, understandable, clear code (a good portion of "knowing what you are doing" is figuring out how to properly encapsulate in a function).

However, most driver programmers don't know what they are doing. That isn't going to change in the term. Rust allows them to write drivers without writing memory leaks or buffer overruns. Net win.

Reiserfs in the Linux kernel. Old one but good one.

Which mental health problems are you thinking of that can be treated successfully?