My M turned upside down. I’m leaving it like this

The newest windows terminal is called “terminal”.

I used to type “cwd”, but after installing terminal, I type “terminal”. Probably same situation for OP.

My comment explicitly avoids the “standard” problem.

A user could have many "theming system"s installed at once, while only having 1 DE. The user ideally would configure only one, and some program should try to translate that system into the other ones.

Then each app will fetch the list of theming systems the user has installed, and choose whichever the app prefers. And if there’s no match, fall back to a default hard coded theme.

You believe that an invading army that commits war crimes and comes from a country with no democracy is going to hold free and fair elections? Are you insane?

I see you ignored my entire comment.

I don’t know what is more explicit about expect. Unwrap is as explicit as it gets without directly calling panic!, it’s only 1 abstraction level away. It’s literally the same as expect, but without a string argument. It’s probably top 10 functions most commonly used in rust, every rust programmer knows what unwrap does.

Any code reviewer should be able to see that unwrap and flag it as a potential issue. It’s not a weird function with an obscure panic side effect. It can only do 2 things: panic or not panic, it can be implemented in a single line. 3 lines if the panic! Is on a different line to the if statement.

An unhanded error will always result on a panic (or a halt I guess). You cannot continue the execution of the program without handling an error (remember, just ignoring it is a form of handling). You either handle the error and continue execution, or you don’t and stop execution.

A panic is very far from a segfault. In apparent result, it is the same. However, a panic is a controlled stopping of the program’s execution. A segfault is a forced execution stop by the OS.

But the OS can only know that it has to segfault if a program accesses memory outside its control.

If the program accesses memory that it’s under it’s control, but is outside bounds, then the program will not stop the execution, and this is way worse.

EDIT: As you said, it’s also an important difference that a panic will just stop the thread, not the entire process.

Replace uncaught exception for unhanded error.

“unwrap should not exist” is true as long as you don’t want to ever use the language. If you actually want to use it, you need it. At least while developing.

Some values cannot have a default value. And some cases it’s preferable to panic even if it has a default value.

unwrap is not the problem. Cloudflare’s usage is.

It’s really hard to do without Rc (or similar) or unsafe.

You can’t shrink the yardstick down to an infinitesimal size.

Coastlines are not well defined. They change in time with tides and waves. And even if you take a picture and try to measure that, you still have to decide at what point exactly the sea ends and the land starts.

If the criteria for that is “the line is where it would make a fractal” then sure, by that arbitrary decision, it is infinite. However, a way better way to answer the question “where is the line” is to just decide on a fixed resolution (or variable if you want to get fancy), which makes the distinction between sea and land clearer.

It is like saying that an electron is everywhere in the universe, because of Heisenberg’s uncertainty principle. While it is very technically true, just pick a resolution of 1mm^3 and you know exactly where the electron is.

Don’t have the source on me now, but I read an article that showed it was surprisingly easy. Like 0.01% of content had his magic words, and that was enough to trigger it.

Formal and informal is not the same in plural.

“Ustedes” is formal, “vosotros” is informal. Although Mexicans (and many other south Americans) don’t use the informal version, it doesn’t mean that it doesn’t exist.

Some countries also say “vos” for singular. I don’t know if that replaces “tú” or “usted” though.

It’s not minor, but commuting. If every job that could be done from home was always done from home, those people would save 100% of their commuting time. They would also leave room so the ones that have to commute can go faster (in case of road) or enjoy more space (in case of rail).

I don’t understand why any user would have to care or even know what GUI toolkit an app uses.

I don’t know why the burden is put on the user/DE. You shouldn’t have to care about what GUI toolkit your DE uses either.

DE and themes should be decoupled from eachother. So the user can install whatever “theming system” they want, and GUI toolkits should aim to support as many theming systems as practical.

GUI toolkits are implementation details, the user doesn’t care about implementation, it cares about what it sees. And what it sees is the colors and icons.

Data storage devices are the last items you wanna buy second hand though. A drive failing could mean much more than just having to buy a new one.

Don’t read too much into it. Sound like he just doesn’t want trump to miss the rest of the speech.

The problem is not the AI integration. Along with AI integration they changed their stance on data selling.

It went from “We promise to never sell your data” to “Firefox is secure!” Just as they were adding AI.

Heh. Ironic.

The problem with that is that reviewing takes time. Valuable maintainer time.

Curl faced this issue. Hundreds of AI slop “security vulnerabilities” were submitted to curl. Since they are security vulnerabilities, they can’t just ignore them, they had to read every one of them, only to find out they weren’t real. Wasting a bunch of time.

Most of the slop was basically people typing into chatgpt “find me a security vulnerability of a project that has a bounty for finding one” and just copy-pasting whatever it said in a bug report.

With simple MRs at least you can just ignore the AI ones an priorize the human ones if you don’t have enough time. But that will just lead to AI slop not being marked as such in order to skip the low-prio AI queue.

I hope they are prepare for the AI slop DDoS. Curl wasn’t, and they didn’t even state they would welcome AI contributions.