We can do this natively in macos, isn’t it?

Yes, mostly, since macOS 15

Yeah I guess, just a bit clunky I think. For $5 Magnet is awesome!

No. Mac window management is inexplicably awful.

Why did they use x86_64 in the article instead of AMD64?

Yeah, that’s pretty much how I see it too.

Cate is not trying to compete with tiling/scolling WMs. Those are better if the main problem is arranging normal OS windows.

The goal here is more project-scoped: one spatial canvas where terminals, browser previews, editors, docs, notes, agents, git/worktrees, and saved layouts live together. More like a persistent workspace for a single project than a global desktop environment.

Forgejo is pronounced as forjeyo

> No borrow checker. No lifetimes. No fighting the compiler for 20 minutes over a string.

I don’t like this attitude, both zig and rust have their strengths.

Rust has bad ergonomics. You will see that "attitude" as long as coding exists, or lifetimes are fixed in a way to allow you to omit them in contexts which are not concurrent or are embarrassingly parallelizable.

it's not attitude that sentence (not x, not y ...) is pure uncut llm slop

"No borrow checker" id not a reason to switch to Zig, unless you have a reason that borrow checker is limiting you from developing, hence the "I don't like this attitude". Just give the reason, not the "solution"

Not to mention we're nitpicking over something that an LLM wrote.

There doesn't really need to be a counterargument. If you like Zig, that's great. Zig is great, you are great. You go on using it.

You should really make sure to take your own advice when you're being this discourteous.

Fair enough

That must explain the projects moving away from Rust then

so Google will be monitoring whatever on the screen continuously or only when the user say the magic words (this, that, here, there)?

Indeed. "AI-enabled pointer" is misdirection. This isn't an AI-enabled pointer; it's sending screen to AI, which yes, includes pointer position. The AI doesn't live in the pointer. The AI lives, apparently, so thoroughly in the system that it can see and do anything, and the pointer is just a way of giving it context.

Google Recall. Hey, it's all about the marketing.

> AI native

What’s that supposed to mean?

My guess is that they expose first party skills and maybe other agent friendly docs? Not positive though.

nice (and clever) name!

I actually expected an unsafe-only Rust because of the name and the "archaic" date (of course, "safe" languages did exist at the time, if not low-level and safe ones).

Still, cool project.

unsafe-only Rust ... good idea!

Thank you!

these are the updated models:

google/gemma-4-31B-it-assistant

google/gemma-4-26B-A4B-it-assistant

google/gemma-4-E4B-it-assistant

google/gemma-4-E2B-it-assistant

for anyone wanting a glossary to explain the naming scheme here:

E4B = 4B effective parameters (using per-layer embeddings)

E2B = 2B (like above)

it = instruction tuned (rlhf and all that jazz)

assistant = Multi-token drafters (the new 2x speed up)

> assistant

naming still hard I see

I wonder if they hadn't decided to call it a drafter when they named the files and were using assistant internally? google being google...

Yes they should have stick with the naming convention.

google/gemma-4-31B-it-ass