47,548 karma · joined September 12, 2010
As they say, qui cum canibus concumbunt cum pulicibus surgent.
Arc's team was disproportionately effected by the layoffs. A lot of the major engineers that worked there changed their Linked in details to list Nvidia, AMD, etc.
As for DC and Workstation GPUs, they also seem to be canceled.
We'll see next year, I guess.
Nova Lake (Series 4) is already too late in development to switch, so its shipping with Celestial, and Titan Lake (Series 5) after it will be essentially a Nova Lake refresh using a hybrid tile that is Celestial's graphics engine with Druid's media, memory, and bus controllers (since Druid development has been halted).
Serpent Lake (Series 6) will be the first that can ship with Nvidia tiles, which should launch in early 2028.
Unless something changes, there will be no DGPU Celestial products.
Unfortunately, the ink on the contract is already dry, so this is the end of Intel's GPU unit.
The side effect is Intel has fired their entire Arc team, including the driver team, as well have canceled all Celestial products (only low end combined GPU + IO die products will have Celestial, as its too late in production to change). All future Intel products will have Nvidia graphics tiles.
Llama.cpp is, of course, still trying to better support the existing Intel products, but its kinda hard when they might stop working any day due to driver breakage.
They both have GDDR6.
The B70 has 256 bit it bus at a clock speed of 2375mhz (608 GB/s), the 3090 has a 384 bit bus at a clock speed of 2438mhz (936 GB/s).
It isn't slower, it just has less channels, ie, it is less wide.
At 48khz, with a tone generator (not rando Youtube videos or anything), you should be able to clearly hear up to around 16khz (as in, can tell pitch of tone), and be able to tell a tone is being played at all up through 18khz, and hopefully up to 20khz.
OTOH, we know nothing of your audio equipment nor how its setup.
Hard to Google for it without getting AI slop on it, but apparently they built their own stack in 2019.
Not sure I like their solution, "Meta-data is persisted in RocksDB databases using a proprietary KV store called QuarkDB." Unless QuarkDB has magically removed RocksDB's amazing ability to corrupt and lose data frequently, this whole thing sounds like a bad idea.
Also, their data is not stored on any one system (local XFS, Ceph, Lustre), a recipe for disaster.
You can have more than one pool.
Seeya sometime next decade.
They are more like a single model that has two separate attention head mechanisms.
Qwen 3.6 shipped with working MTP first, and had working MTP in llama.cpp first.
He's right to buy American made when it comes to cars, we know what we're doing... he's just gonna have to buy a Toyota to get American.
Of domestically produced GM, Chrysler, or Ford vehicles, most are shipped to foreign customers; of domestically sold GM, Chrysler, or Ford vehicles, most are manufactured by foreign factories. They do some assembly locally, but the majority of it is of foreign manufacture.
However, Toyota manufacturers most of their domestic sales domestically, and operate one of the largest car manufacturing plants in the US, only slightly below Ford's US plant that largely exports to Europe. Of domestically made cars that are domestically sold, Toyota dominates that.
BMW and Nissan also operate plants in the US for domestic use.
I agree that this backwards Reaganite behavior is just going to further shut the Detroit Three out of any future. They're already on the way out, a slow decline since they left the US, but this is going to finally finish those zombies off.
Yes, classic Qt Widgets still doesn't allow for hardware acceleration.
However, the majority of Qt UIs you deal with are in Qt Quick, which is hardware accelerated. Almost all of KDE is Qt Quick, for example.
And, btw, the reason Microsoft even bothered is because (dun dun dunnnn) lots of internal apps at Microsoft were written with Qt, not MFC, and leadership got pissed when they realized (they couldn't tell the difference, since Qt does the native++ technique).
As for Linux, yeah, thats a shitshow. Qt was closed source, Linux isn't, so they made Gtk, but then Qt got open sourced, and then the Gtk guys just kept going. Qt can mimic Gtk3/4 themes and already uses 100% native rendering (same APIs Gtk does).
People keep writing Gtk apps for some reason, and I don't know why. I can get the C++ hate, but Qt has the cleanest C++ I've ever seen.