[0] https://en.wikipedia.org/wiki/John_Gilmore_(activist)#Activi...
5,911 karma · joined June 4, 2019
[0] https://en.wikipedia.org/wiki/John_Gilmore_(activist)#Activi...
Compromised OpenVSX Extensions:
codejoy.codejoy-vscode-extension@1.8.3
codejoy.codejoy-vscode-extension@1.8.4
l-igh-t.vscode-theme-seti-folder@1.2.3
kleinesfilmroellchen.serenity-dsl-syntaxhighlight@0.3.2
JScearcy.rust-doc-viewer@4.2.1
SIRILMP.dark-theme-sm@3.11.4
CodeInKlingon.git-worktree-menu@1.0.9
CodeInKlingon.git-worktree-menu@1.0.91
ginfuru.better-nunjucks@0.3.2
ellacrity.recoil@0.7.4
grrrck.positron-plus-1-e@0.0.71
jeronimoekerdt.color-picker-universal@2.8.91
srcery-colors.srcery-colors@0.3.9
sissel.shopify-liquid@4.0.1
TretinV3.forts-api-extention@0.3.1
Compromised Microsoft VSCode Extensions: cline-ai-main.cline-ai-agent@3.1.3No, that's speculative execution you just described. Branch prediction was implemented long before out-of-order CPUs were a thing, as you need branch prediction to make the most of pipelining (eg. fetching and decoding a new instruction while you're still executing the previous one--if you predict branches, you're more likely to keep the pipeline full).
Technology allowed companies to expand and centralize on a national scale, and capital pushed that to the conclusion we're at now, where there are a few gigantic players (at most) and almost all recourse against bad faith has been precluded. Nowadays if a customer is taken advantage of, they can't drive 5 extra minutes in the opposite direction and take their business elsewhere, or shame the owner in the local paper. Only impenetrable monoliths remain.
Searching https://pkgs.org says that most distros don't have a gtk 1 package... except for Slackware!
LLMs are text generators that are very good at writing a book report based on a prompt and the patterns learned from the training corpus, but it's an entirely separate problem to go through that book report statement by statement and determine if each one is true/false/unknown. And that problem is one that the AI field has already spent 60 years on, so there's a lot of hubris in assuming you can just solve that and bolt it onto the side of GPT-5 by next quarter.
Also SIMD is just one example. Modern DMA controllers are probably another good example but I know less about them (although I did try some weird things with the one in the Raspberry Pi). Or niche OS features like shared memory--pipes are usually all you need, and don't break the multitasking paradigm, but in the few cases where shared memory is needed it speeds things up tremendously.
And lower power usage. Datacenters and mobile devices will always want that.
The same could be said for, say, SIMD/vectorization, which 99% of ordinary application code has no use for, but it quietly provides big performance benefits whenever you resample an image, or use a media codec, or display 3D graphics, or run a small AI model on the CPU, etc. There are lots of performance microfeatures like this that may or may not be worth it to include in a system, but just because they are only useful in certain very specific cases does not mean they should be dismissed out of hand. Sometimes the juice is worth the squeeze (and sometimes not, but you can't know for sure unless you put it out into the world and see if people use it).
Bluesky is a small team of like ~30 people, if they keep running lean they have at least a chance of a decent profit margin. But none of that will make anyone a multi-billionaire, so never mind.
That really makes three companies that are happy to concede to nVidia, because Apple could definitely challenge nVidia if they wanted to.
Note: I'm not saying that AMD sucks, just that their corporate culture prevents them from being very ambitious.