I’m sure the other commenters are right, but I’m guessing market segmentation may play a role here too.

Does this work inside of Podman containers?

> opencode with the telemetry stripped out

Care to share? This happens to be important to me and I’m sure I’m not the only one (as evidenced by Github issues).

Did you also change the other questionable behaviors?

No really, no. the last thing Github needs is yet another vibe coded fork of a mostly vibe coded app in the first place.

If I ever get around to vibe rewriting-it-in-go I might share that.

I agree with the theory and maybe consumers will too. But damn, the actual products are bad.

Wow, just like its larger brother!

I had a similarly bad experience running Qwen 3.5 35b a3b directly through llama.cpp. It would massively overthink every request. Somehow in OpenCode it just worked.

I think it comes down to temperature and such (see daniel‘s post), but I haven’t messed with it enough to be sure.

This is why the EU regulates them (or pretends to) as a public utility. The individual action I took was to donate to Fairlinks‘ legal fund.

No word on weights.

Is this the end of Qwen as cool local models?

It's a point update to the closed-weight Qwen3.5-Plus. Of course there are no weights. Alibaba has consistently not released weights for their best models.

I see it for that exact reason. It’s still a huge name and will definitely get people talking. Of course the product will have to live up to it.

„By the creators of Skype“ would of course also carry significant weight.

Microsoft really has nothing to fear ...

Why is that?

Office is still a core product, is it not?

I missed this. So they didn’t really solve much at all. I guess at least it’s compatible with other runtimes. But yeah, who would’ve guessed that Cloudflare software would (besides being vibeslop) prefer Cloudflare infra. This, of course, makes the software quite hard to adopt.