We care about specifically Chinese models, because China distills our models. And that's real competition. So we want to ban those.

PS. Oh yeah, in case any open non-Chinese model will one day be good enough to compete with us, we will want to ban you as well, just FYI.

Kthxbye.

Win95/98 was very efficient in this area. Too much empty space wastes the space.

Forking an "embarassing project" is really something.

Edit: Huh? Downvote explanations are welcome. I wrote only what Andrew Kelley wrote.

But also, even if a device doens't support DHCPv6 IA_NA, you can always also have a DNS server in your network, and you can bind SLAAC-generated Android addresses to simple subdomains. This seems better than DHCP anyway.

They of course also have a DS-Lite AFTR gateways to tunnel the IPv4 traffic. In practice, everything works (for me at least).

Legislations define rules to protect "us" from harm, but police is for policing only.

They do not protect people. They protect the law.

Am I not allowed to say that hammer is just a tool and it matters how you use it? Because it makes all classic sculpture art meaningless? No it doesn't.

The "car is just a tool" doesn't make oil waste problem any less problematic.

I am one of those people who say AI is just a tool and it matters how you use it. But also, GCC/Clang/Rust are just tools and it matters how you use them. Your mouth is a tool and it matters how you use it. When thinking about ANY tool you should think about the best way to use it.

But for AI specifically this saying is most important, because a lot of people treat AI as another person. "He's like a junior employee" is what I've heard in my company on meetings. It's not a he, it's not a junior, it's not an employee. It's a tool!

Equivalent of what.cd today is RED.

But, TBH, most of the pirated music today is on YouTube anyway.

But to write about it publicly, manifesting our ignorance and lack of critical thinking skill? It's an entirely different matter.

Let's say the supervisor wants you to write a new microservice. Do you refuse to do it because the supervisor smokes cigarettes and you're an anti-smoker? I think that if you have objections, you should refuse only on technical grounds, not personal.

Because a lot of mechanisms actually still have guards in runtime. And using .clone() on Rc/Arc is actually the idiomatic/preferred way of evading the borrow checker if we can't design the data structure in a different way.

It's a big difference between cases when you need to spend brain energy to find ways to "out-smart" the compiler, and spend brain energy to "fit into the proper set of assumptions" of a programming language.

Also it doesn't guarantee that the code is always 100% correct.

But I think this is the correct direction of programming language evolution.

The whole point of the borrow checker is to make it impossible to write wrong code. If Zig accepts bad code, but assumes people will have self-discipline to maintain it, how is that different from C?

C assumes good discipline, as well as C++. But it will happily accept bad code. So I'm not even sure what Zig is even improving on.

Rust was designed to answer this exact problem (among a few others of course).

So the argument "your code is fscking sheet" is very 1990's. In 2026 we need guarantees that we can't produce invalid code.

https://bun.sh/blog/bun-in-rust

So sometimes hidden control flow is needed.