You also have the sonar/radar thing on the camera which can measure distance. Can that be hooked into focus so it's automatic?

If you’re going to go through all that trouble you may as well just use a lens or cam body with a quality, built in AF. Way cheaper and the tech has matured greatly. Plus even with lower to midgrade cameras it’s easy to find a capable system with a solid codec you can color match enough with the rest of the movie. Even my GH6 I travel with can shoot 5.7k pro res

How does evolution learn the form-fitness relationship?

It's the same thing here, you randomly try various token-relationship values and the ones which are slightly better will be favoured.

That's easy to say AFTER you know the architecture.

Einstein special relativity is taught these days in high-schools. Doesn't mean it wasn't the very hard part at some point in time.

As they say, shoulders of giants.

Isn't that over-simplifying it a bit too much?

You can go another step - a FFN can be simulated on a Turing machine, thus it just exemplifies the incredible semantical power of the Turing machine model of computation. (in fact you don't even need a Turing machine, since there is no looping in one forward pass).

In theory you can run a huge FFN on the tiniest Turing machine, in practice it's much better to run a Transformer on the latest NVIDIA hardware. Or as they say "quantity (performance) has a quality all its own"

I was about to post your last point / quote. Going multigpu is relatively not so though but once you go multi-node you have distributed storage/io/compute system which is highly non trivial. Add that the long training times now you have robustness/fault-tolerantness concerns with hardware failures and restarts. Today’s training systems are engineering marvels.

Good point!

There is also the case for Markov chains being theoretically able to do these if tuned well. Or even SAT problem.

"LLM is just fancy autocomplete"

Google already released specialized drafters for Gemma 4.

The E2B ones? Or what do you mean by specialized drafters?

They have -assistant in the name, so e.g.: https://huggingface.co/google/gemma-4-31B-it-assistant

Thanks

The “-assistant” models released by Google are specialised tiny MTP draft models :)

31b-it-assistant is what enables MTP

Google already did

https://huggingface.co/google/gemma-4-26B-A4B-it-qat-q4_0-un...

This is safetensors. Is there any way to run these on a Mac paired with the MLX QAT?

(Pardon my ignorance; this stuff moves so fast)

Did you see this?

https://point.free/blog/gemma-4-on-a-2016-xeon/

Xeon, but could be useful for MTP on Mac.

I hadn't seen this, thanks.

I do have the Qwen 3.6 (35B) MTP implementation running (in LM Studio; it doesn't need a separate drafter), along with non-MTP Gemma 4 26B, and I can see that Unsloth Studio can run the new QAT, but I can't see how you can run the assistant/drafter. Yet.

It's just a constantly changing landscape. Don't get me wrong, it's fascinating and for various reasons I am pleased I can keep up even slightly, but eeeehhh :-)

Yeah — that is the base QAT model, and there are safetensors weights for the QAT version of the MTP drafter, but there are no MLX/GGUF versions. I think the answer is a combination of:

1) Gemma 4 MTP is too fresh for off-the-shelf software to use anyway

2) "you can convert them yourself" which is fine, obvs

Agent can get tricked into using a malicious library in your project, commit and push that, which you then run outside the VM.

So if you ever run the repo code outside the VM and don't review everything committed, you are still at danger.

It doesn't have any credentials inside the VM though, not even for git, so it could commit but not push. And I manually review/commit/push outside of the VM since I don't want to just dump stuff without reading it first.

But good call-out if someone uses a different workflow.

The un-quantized MoE outperforms it.

But between same (V)RAM requirement 4 bit 26B-A3B and 8 bit 12B it's unclear which one will win, especially given one is MoE and the other dense.

All the launch benchmarks are at 16 bit.

Evangelism for AI. Google is one of the big AI providers.

Eventually the local model is not enough, and you'll upgrade to the big ones.

"Background removal" or "Face aging" without AI were done before, and they were shit.

Putting "AI" into the feature title means "this time it actually works"