Fun fact: Qwen was not initially a Apache Licensed project, it was based on a custom license from Alibaba that restricts commercial use: https://github.com/QwenLM/Qwen/blob/ba2d85a13b28ed1ee0dde2d6.... There's no guarantee that they won't just switch it back later.

Kudos for them for switching to Apache License, of course. BUT, they're still a for-profit company. So as DeepSeek btw.

Why? Because they said it a few times? Then if they know the risk, why do they still making it? Comes out the "some one will do it eventually, better be us 'good' people to do it first" talking point?

See? It is a marketing strategy after all. These all talks, it's all to fit themselves into the "'good' people" narrative. It's a centuries old strategy to shield it's user from responsibilities while luring the support from the stupid.

However, the most harmful damage, which is mass layoffs, is already partially done. This could really kill, a massive genocide even, by making people jobless and potentially incomeless. And it is shown that these tech CEOs, they don't care any bit of that beyond the point "I've already told you so".

OR, the OS might kick in and throw a segmentation fault etc, often with some information associated to it.

Again, if a LLM can output 100% correct code, no bug of whatever kind should exist. Seeing a segfault could just invalidate that assumption completely and definitively. That's the point.

> Rust guarantees lack of undefined behavior in safe code

And that don't guarantee heisenbug-free, that just means your heisenbug was fully checked by Rust compiler and is now managed by the language runtime/facilities.

So, now instead of a crashed program and a "sever" DoS vulnerably, you got a disconnected user every time they trigger the bug. The user might assume it's the network, so does your logging stack. After a few times, the user starts bitching about your stupid network, and left for your competitor's product, while you busily trying to figure out why the network suddenly ain't as good as it used to.

> 70%[1][2] is tiny?

It really depends on how they define what counts as "vulnerably", or in Chrome's case, "'high severity' security bugs" which is very specific. Microsoft probably have many decades-old code written before the invention of better checkers, that contributed to the problem.

Memory safety is just a tiny part of over all security. If a LLM can transcode correctly, then it should also output 100% correct C code.

On the other hand, If a LLM cannot correctly transcode, then using Rust may just make the bug soundless, because the language runtime/code-gen "avoided" usual punishments that might make the bug (and bug report) obvious.

It kinda was fun, like a very patient professor stand right besides you. It was the one of the best math learning experience I've ever had, and you don't even need to send bribe/gift to Gemini to keep you in it's favor.

On the other hand, if you ask a LLM to completely finish the work without thinking it through by yourself, then it sounded like cheating, to yourself.

I'm a Chinese, from what I learned, you probably don't see the situation clearly.

The problem is influence. America wants to solve the Cuba (and Iran) problem since very long ago, and right now, while China is busy patching up their economic slop/mismanagement and Russia is trapped in Ukraine, is simply the best time to do so.

With Cuba is cleared out, the Americas continent will be cleared of major (and loud) threats against America. That alone is beneficial.

It's the same but opposite reason why America is supporting Japan, Taiwan and Europe etc, to control the influence of their competitors like China, Russia, India, Brazil etc (a.k.a Global South). It also allow Americans to keep a tap on Japan, Taiwan and Europe (etc) so they remains in American control.

That's probably the 4-D chess you talked about.

Also, the "Trump the 'Nation Builder'" part: In China, "Nation Builder" was a popular forename, it means "someone who contributes to their own country/nation". In the Trump context, it means that Trump's policies is benefiting China's goal. That is, when compare to Biden's policy which is much sophisticated and on point (while Trump's is blunt and wasteful).

But I don't think American's soft gesture towards China will last after Cuba and Iran is dealt with (if) in a American victory though. Unlike what the "New World Order" conspiracy suggests, I don't think this world is stupid enough to not to pursue the maximums goal when possible. That's probably why Americans are working towards the maximums goal inches by inches.

Don't over interpret this. You can also weaponize efficiency too, just like what USSR did to itself, hyper optimizing their industrial sector and leaving everything else to a free dry.

Truth is, keep something alive is just hard. It dies if you overdo, and it also dies if you underdo. A sabotage could just tip the balance, that's all.

It's really a system design problem rather than access control: if you separate functional modules in a reasonable way, then it can be better reused.

A lot of libs/packages in Go's stdlib also has this problem. They like to package everything in a very tight interface (very obvious example includes crypto/* and http), without exposing implementation detail to the end user.

Doing this of course has it's benefits, but if the feature provided by the stdlib slightly don't fit you needs, then you might have to write your own (potentially unsafe and/or less performant) one from zero.

Rust is great overall, but there's some oddities. For example their lib.rs / `mod` is very, very unintuitive, it felt overdesigned and unnecessarily complex (just see [their book]). I like what Go or Java did to their lib/package systems, it's much better that way.

[their book]: https://doc.rust-lang.org/stable/book/ch07-05-separating-mod...

But then people started to actually use it to build big sites, `echo($_GET['user'])` alone is not enough, it has to be:

   is_valid(new Integer(0, 100), $source, $name);
   } // Or something like that, hasn't write a single line since PHP5.