copacetic

Puh, this took me a while to understand, so I'll try to summarize:

1. Big Tech likes to use cookie banners to annoy people to consent to tracking
2. EU proposals says they must accept a machine-readable opt-out as well
3. Google lobbies via countries to remove that part from the proposal
4. It's up to the EU parliament now

"I have five pounds. Is that enough?"

"No."

"It costs more than five pounds?"

"No."

"How much do I have to pay?"

"This is NaN pounds."

"That means it costs more than five pounds?"

"No."

"It costs less than five pounds?"

"No."

"Exactly five pounds?"

"No."

leaves the shop

(Remember, comparison with NaN is always false)

Wikipedia says "Participation in the contest is primarily open to all broadcasters with active EBU membership", so I would think so.

The usually converts a lot of mindsets from "let's build the future" into "fight for dwindling resources" and results in a quite toxic community.

Looks like a normal branch where someone debugs some GitHub workflow.

Sounds like Iran won the war the US started.

Germany sells tanks to Israel?

I find that Germany sells air defense systems, communication equipment, anti-tank weapons, and ammunition. Also, a license for a V12 engine used in Israel's Merkava tank.

Quite a while ago, I wrote this to document my understanding what OOP actually is.

This sentence at the end is interesting:

On the other hand it sounds unlikely that there will be a popular language without object-oriented influences some day, so at least minimal syntax-level support is desirable.

Rust was published like one year later and it can be considered popular by now. Does Rust support OOP via traits? Kind of yes, but so does Haskell with typeclasses.

Most C++ devs blame themselves and not the language though. So it still gets used a lot.

To be clear, the language itself is usually not the big part. You also have to learn the eco-system, libraries, packaging, debugging, etc.

(C++ is still a very "comprehensive" language though)

If you use the SQLite C API like this

    char query[256];
    snprintf(query, sizeof(query),
             "SELECT * FROM users WHERE username = '%s'", username);
    int rc = sqlite3_exec(db, query, NULL, NULL, &err_msg);

and someone enters Robert'; DROP Table Students;-- as username, it deletes the table Students.

    const char *sql = "SELECT * FROM users WHERE username = ?";
    int rc = sqlite3_prepare_v2(db, sql, -1, &stmt, NULL);
    if (rc != SQLITE_OK) {
        fprintf(stderr, "Failed to prepare statement\n");
        return;
    }
    sqlite3_bind_text(stmt, 1, username, -1, SQLITE_STATIC);

Using this "prepared statement" and "bind", your code is secured against such SQL injection attacks.