Maybe: Christian Rocha

Backward Deployed Engineer • Founder @charmcli • At least 50% notes to self

[Maybe: Christian Rocha @meowgorithm]

Conversation is 50% listening and 40% discerning what not to say.

[Maybe: Christian Rocha @meowgorithm]

Or as we’ve been saying internally, CheapSeek

[Charm @charmcli]

We’ve upgraded DeepSeek V4 on Hyper.

Faster. More reliable. Significantly cheaper.

Zero data retention, always.

[Maybe: Christian Rocha @meowgorithm]

Now I see the full picture

[Charm @charmcli]

Qwen 3.7 Max is now on Hyper.

We waited a week to make sure it met our standards for performance and zero data retention.

This one is impressive. Try it here:
⚡️ https://t.co/pTUfhEzwM7

[Maybe: Christian Rocha @meowgorithm]

@tweetatweir Same. Honestly I miss coding Elm quite a lot.

[Maybe: Christian Rocha @meowgorithm]

@kwuchu Oh very nice

[Charm @charmcli]

Using Hyper in Crush is a piece of cake.

[Maybe: Christian Rocha @meowgorithm]

@willmcgugan You know why

[Maybe: Christian Rocha @meowgorithm]

This one is so fun. Crush can run over unix domain sockets, named pipes on Windows, and good ol’ TCP.

[Charm @charmcli]

⚡️ Crush now has multiuser support, currently available as a preview.

This is part of a broader client-server system we're building into Crush.

Enable it with:
CRUSH_CLIENT_SERVER=1

[Maybe: Christian Rocha @meowgorithm]

@willmcgugan The other thing is, like, Claude knows all the Eurovision contestants and their personal backstories for the past 70 years. That makes it slow and expensive.

I do believe there’s a future where a swarm of small, focused models will reign supreme.

[Maybe: Christian Rocha @meowgorithm]

@tauraamuix TBQH, I don’t think home-manager is true to ‘the Nix way’.

NixOS manages packages just fine. Mutable user config is absolutely lovely and can simply live in version control as needed.

Also, ‘nix profile’ is a thing now, and might make more sense to wrap, if anything.

[Maybe: Christian Rocha @meowgorithm]

@CyphrRiot I love this project. OpenBSD is totally under-appreciated

[Charm @charmcli]

Hyper is here.
Purpose-built AI inference for coding agents.

Currently in private beta.
https://t.co/pTUfhEzwM7

[Maybe: Christian Rocha @meowgorithm]

@tweetatweir They’re all wanna-be Subarus

[Charm @charmcli]

Antigravity is built with Bubble Tea and Lip Gloss.
https://t.co/ybjLpXWGXb

[Charm @charmcli]

Hyper. Soon.

[Maybe: Christian Rocha @meowgorithm]

@ivanburazin Perhaps AI agents will download warez instead

[Maybe: Christian Rocha @meowgorithm]

@steeve Oh now we’re talking

[Maybe: Christian Rocha @meowgorithm]

Real talk, all the way through

[Mitchell Hashimoto @mitchellh]

It isn't unexpected that the focus of the Bun Rust rewrite is on the anti-Zig side more than anything, since the internet loves to hate. What is unexpected and unfortunate is that leadership within Bun hasn't tried to steer the conversation away from that at all.

There are so many positive and interesting takeaways from this and I'm not really seeing any of them pushed as the primary message.

A positive thing that hasn't been talked about at all is how far Bun came thanks to Zig. And even if you dump it now, its meaningful for how good Zig was to even build a product to this point and impact by any metric. I would've loved to see anyone in leadership say this.

On the interesting side is how fungible programming languages are nowadays. Programming languages used to be LOCK IN, and they're increasingly not so. You think the Bun rewrite in Rust is good for Rust? Bun has shown they can be in probably any language they want in roughly a week or two. Rust is expendable. Its useful until its not then it can be thrown out. That's interesting!

There's been a lot of talk about memory safety and no doubt Rust provides more guarantees than Zig. But I'd love to see a better analysis of why Bun in particular suffered so much rather than take the language-blame path. How could engineering as a practice been more rigorous to prevent this? What were the largest sources of crashes other programs should watch out for? How does Rust prevent them? How could Zig theoretically prevent them? That's interesting.

I know the official blog post hasn't come out yet from Bun. But they're smart enough to know that that PR would stir up controversy the moment it opened, or they should've been. And plenty in the company have been tweeting and writing about it. Its somewhat telling to me in various dimensions what they chose to talk about first.

I tend to think I'm pretty good at corporate PR/comms (especially when it comes to developer audiences) and I think appealing to the negative is never the right long term strategy; it does work to get short term eyes though.

[Maybe: Christian Rocha @meowgorithm]

Please don't do this, @AnthropicAI. It prioritizes the wrong things. I know you can do better than GitHub here.