Capsicones

Not to cause any "offence", but I think that "manoeuvre" would cause misspellings for you if you need to write something in American English, say a paper or a formal document. Best double check your spell checker locale, and make sure your words aren't incorrectly "labelled" as you "centre" your text.

Having the default spell check as en_ca would be a problem through. I'd have an "axe" to grind in this case, as I challenge the "honour" of hunspell. I usually just manually choose metric units and a 24 hour clock on top of en_US.

Chinese phonology doesn't allow for the pronunciation of "app", for example. I see a lot of Chinese people spelling it as "APP", and pronouncing it accordingly. It's kinda funny to me, since the Mandarin word "yingyong" is only two syllables. "APP" just seems more cumbersome by all account, yet it has become inexplicably popular.

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 liked the UI of Evolution when I used it, but there were some usability issues which made me switch to Thunderbird in the end. There's a good extension in Thunderbird for markdown support when composing emails, which I could not use on Evolution. And Evolution failed to attach .eml files when I tried that (as opposed to including previous emails inline). But if your email use case is very basic, it should be fine.

I don't see a fundamental difference, only that "reactionary" is favored more by leftists, and "regressive" more so by liberals. I myself would use the two interchangeably, depending on the preference of the person I'm talking to.