Weerasak

Go-to-Rust migration guide you've been waiting for. 🦀 Matthias Endler from corrode.dev just published one of the most honest, practical guides on migrating backend services from Go to Rust. No hype. Just real trade-offs: ✓ nil panics → Option ✓ -race flags → compile-time Send/Sync ✓ if err != nil → Result + ? ✗ Goroutines → async coloring (the real pain point) ✗ Go compile times → Rust compile times (honest warning) Also covers ecosystem mapping, integration strategies, and when to keep Go. 🔗 corrode.dev/learn/migratio… #Rust #RustLang #Go #Golang #BackendDevelopment

From @josevalim's first commit to millions of lightweight processes running in production — happy anniversary @elixirlang! 💜

The full video for our "fireside chat on the evolution of developer craft" is live: youtube.com/watch?v=VTYx7E… with @rseroter @the_thagomizer & Ciera Jaspan

🚀 Just launched: ExtendDB — an open source DynamoDB-compatible adapter written in Rust. ✅ Full wire-protocol compatibility ✅ PostgreSQL storage backend ✅ Pluggable architecture for more backends ✅ Works with existing AWS SDKs & CLI Apache 2.0 | v0.1 — come build with us 🛠️ go.aws/4fzBl2C

@shengzheyao @rakyll Why it is not Opensource like Gemini CLI ?

Antigravity CLI 1.0.1 is out. Key updates: - Fixed OAuth not persisting in some environments. - Enhanced the visual experience on Windows. - Added the new "proceed in sandbox" permission control. Restart agy to auto update or run “agy update". See the full changelog for details: github.com/google-antigra…

Gemini 3.5 Flash changed how I interact with command line tools. It’s so fast that I find it faster to use it rather than typing even the simple commands.

@javarevisited Why it works fast even on computers with much smaller amounts of RAM than 20GB - stackoverflow.com/questions/9300…

“Introducing the pkg.go.dev API” by Ethan Lee, Hana Kim, and Jonathan Amsterdam — go.dev/blog/pkgsite-a… #golang

13 great books on Rust systems programming - that you can get for around 4% of the cover price right now! I especially like the theme of Creative Projects for Rust Programmers - learning Rust by building projects is the genesis of my Coding Challenges project. 👉 The Rust Programming Handbook 👉 Asynchronous Programming in Rust 👉 Rust Web Programming 👉 Design Patterns and Best Practices in Rust 👉 Hands-On Concurrency with Rust 👉 Rust The Practical Guide 👉 Rust for C++ Developers 👉 Game Development with Rust and WebAssembly 👉 Rust Web Development with Rocket 👉 Speed Up Your Python with Rust 👉 Creative Projects for Rust Programmers 👉 Practical Systems Programming for Rust Developers 👉 Rust for Blockchain Application Development You get all of these worth over £368 for around £14 right now through Humble’s Book Bundle and support charity, details here: humblebundleinc.sjv.io/WOd9WX

@eniolps The Go team that works on the stdlib has a pretty legendary quality/stability/security track record too.

Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored). If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update! I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it. Feeling pretty swell about this mentality with all the supply chain attacks happening.

The one that cracked category theory for me, too.

Go ❤️s #GoogleIO! This year, Go team members @cameronbalahan and @muncus presented Go’s product keynote, “What’s New in Go,” where they got into everything we’ve launched in Go 1.25 and Go 1.26, like the new Green Tea GC, native SIMD, deterministic code modernizers in the new go fix, and more! Check it out 👉 youtube.com/watch?v=l4lneZ…

i think the golang function multi-value return is the best way to handle error.

Elixir v1.20.0-rc.6 is out and it implements inference across applications, fully delivering on the ~15 weeks roadmap established at the beginning of the year. Please give it a try, it should be our last stop before the actual v1.20.0 final: elixirforum.com/t/elixir-v1-20…

Linus Torvalds doesn't think AI will replace programmers. Speaking at recent North America edition of Open source summit, Torvalds argues: "I'm personally 100% convinced that AI is changing programming, but it's not changing the fundamentals." Just as compilers increased productivity "by a factor of 1000," He estimates that "AI will increase your productivity by a factor of 10," but insists "AI is great, but AI is not changing programming." Instead, he contends, "a lot of people will use AI to generate the code that the compilers use to generate the code that the assemblers then use to generate the machine code. This is revolutionary in the same sense that we've seen revolutions before." Agree with him?

Why is Rust different than many/most programming languages? Alice Ryhl works on Google's Android Rust team, is a Rust language team advisor, and is a core maintainer of Tokio (the most widely-used async runtime in Rust) Timestamps: 00:00 Intro 04:09 Tokio: an overview 05:11 What Alice likes about Rust 12:48 Rust for TypeScript engineers 13:51 Moving from C++ to Rust 14:34 Memory safety 18:12 Garbage collection tradeoffs 21:46 Ownership, references, and borrowing 26:59 Unsafe in Rust 31:21 Crates and Cargo 35:55 Language design and RFCs 43:02 Building new features 46:30 Editions vs. versions 49:47 Getting paid to work on Rust 51:27 Contributing to Rust 53:03 Rust in the Linux kernel 55:45 AI use cases for Rust 1:01:35 Learning Rust 1:03:54 Book recommendation Brought to you by: • @AntithesisHQ – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. antithesis.com/pragmatic • @sentry – application monitoring software considered “not bad” by millions of developers sentry.io/pragmatic Three things worth knowing about Rust: 1. Rust was designed to turn implicit failures into compile errors. Where other languages allow you to forget something, Rust makes an omission into a compilation error for things like null checks, uninitialized variables, or error propagation with the ‘?’ character. If you mess something up, it’s almost certain your program will not compile. If it does, at the very least you should see a lint warning. 2. Refactoring in Rust is safe and easy, thanks to the compiler. Alice: “I change a return type or struct field, then just fix the compiler errors until the compiler stops shouting. And then once I’ve done that, I’ve updated every place I need to update.” Rust’s focus on correctness makes refactoring it more straightforward than dynamically-typed languages and Java-style typed ones are to refactor. 3. “Editions” allow Rust to make breaking changes without ‘breaking’ anyone’s code. Rust editions (2015, 2018, 2021, 2024) can be mixed freely across crates. A library on the 2021 edition works seamlessly with a binary on the 2024 edition. This is how Rust evolves syntax (like adding async/await as keywords) without forcing an ecosystem-wide migration. Thanks a lot, Alice for this great discussion! And for your work on Rust.

Today, we are enabling this layer on your own compute. This work motivated us to bring new primitives to Kubernetes for session-tenant, stateful, resumable and sandboxed execution: Agent Substrate. AX directly uses Substrate and can schedule directly from the agentic loop.

See github.com/google/ax for an early overview of what we are doing. Productionizing complex long running agentic workloads is inherently hard. Last year at Google, we developed and battle-tested various new systems patterns while developing our internal runtime.

🌟 Today, we are releasing Google’s open source distributed agent runtime. Agent Executor (AX) is a general purpose runtime and aims to solve dynamic scheduling, resumption, auto recovery, auditing, and trajectory branching from kernel snapshots in agentic workloads.