That's very good. Once I wanted to compile Firefox myself for some reason I no longer remember, but their Mercurial-based system was a hassle to work with. Most of us are already familiar with git. So, I know I'm going to be more inclined to make code contributions now that it uses git.

Just wish they could've chosen another git-based option like Codeberg, or even an internally-hosted server. I'm rather wary of GitHub/Microsoft swallowing up so many open source projects.

The paper was published by IEEE and with professors as co-authors. Only the second author is a student. And I wouldn't dismiss it out of hand like that because of a magazine article. Students come up with breakthroughs all the time. The paper itself says it disproves Yao's conjecture. I personally plan to implement and benchmark this because the results seem so good. It could be another fibonacci heap situation, but maybe not. Hash tables are so widely used, that it might even be worthwhile to make special hardware to use this on servers, if our current computer architecture is only thing that holds back the performance.

Edit: author sequence

Some commenters on this post are clearly not aware of PTX being a part of the CUDA environment. If you know this, you aren't who I'm trying to inform.

There seems to be some confusion here on what PTX is -- it does not bypass the CUDA platform at all. Nor does this diminish NVIDIA's monopoly here. CUDA is a programming environment for NVIDIA GPUs, but many say CUDA to mean the C/C++ extension in CUDA (CUDA can be thought of as a C/C++ dialect here.) PTX is NVIDIA specific, and sits at a similar level as LLVM's IR. If anything, DeepSeek is more dependent on NVIDIA than everyone else, since PTX is tightly dependent on their specific GPUs. Things like ZLUDA (effort to run CUDA code on AMD GPUs) won't work. This is not a feel good story here.

The term "rice burner" originated in the Anglo-American context, and the word "ricing" cannot be divorced from the way people use "rice" as a versatile and generic racial epithet in varied context outside of the software world. As in people going, "haha, rice" something when being racist against Asians. It's a long and ignominious American tradition to demean racial minorities with food. As in insulting Mexicans with "bean". Anecdotally, some older Italians still remember being made to feel bad for eating pasta, when Italians weren't white yet. The term "ricing" will certainly remain racist due to the way anti-Asian racism continues to work. Hence my point that the term must be abandoned, if one wishes to not be racist. Just find a different word for it. it ain't that hard. It is certainly not possible to use an American word with racist origins without divorcing it from the cultural context from which it came.

It is clearly racist. "Ricing" comes from a derogatory term for Asian racing vehicles. You cannot excuse the racism inherent to it by personal ignorance. It's the same logic as black face being racist, whether you're personally aware of the history behind it or not.

Though I no longer live in the US, as an Asian computer scientist, I am quite aware of how it is clearly perceived as a racist term by many Asian Americans. To me, it will also never stop being offensive. So, please, stop with this "ricing" stuff.

You can look up Eric Hartford on Huggingface for more info.

Basically, somebody removes such restrictions from models, and publishes uncensored ones under the name "Dolphin". Presumably, an uncensored Deepseek would be called something like "Deepseek R1-dolphin". The full Deepseek R1 is quite large, and I'm not sure when this will happen yet. But there are other great Dolphin models.

Some models like Meta's Llama are way too censored to be useful for many completely normal use cases, and the guy is doing God's work in my opinion.

I do not assume that the US will continue to be a reliable trade partner going forward. Your logic works in a world with rational actors, where trade between Europe and the US is desirable. However, with Trump as President, the US is clearly ceasing to be a rational actor. It is desirable for the EU to cut back its dependence on the US. It would be bad for the incoming administration to be in a position to coerce Europe through economic means.

Also, by failing to control its monopolistic enterprises, many US tech companies are trampling over the rights and privacy of EU citizens. It is desirable for us to cultivate homegrown options, rather than continuing to let American megacorps walk all over us. Reducing trade volume is a rational choice, despite the short term economic pains.

There are political arguments for tariffs. I don't think your economic arguments are likely to persuade too many. In a more rational world, I'd agree with you. And I do very much regret that it has come to this point where I'm in favor of protectionism from the US.

And I thank you, Norah. As an Asian woman, any Linux space can feel pretty unwelcoming sometimes. Most of the time it's the sexism, but this insistence on saying "ricing" is just another reminder that many in this space enjoy a bit of racism on the side, too.

I don't usually say anything; I'm personally too afraid of being dragged into an endless "debate". Perhaps a bit cowardly on my part. So, I appreciate you pointing it out first.

It's still racist when you make it an acronym. We know the term originally came from a racist term for Asian vehicles.

Machine learning pays my bills, and I never had a choice on my graphics card brand. To be sure, I wanted an AMD for the open source drivers, but CUDA remains essential to me. RocM support from AMD is a joke, and isn't anywhere close to an alternative. Reseachers release code that only runs on CUDA for a good reason. To say that I don't get to complain is going too far