Anton Zhiyanov

New interactive mini-book: Go concurrency distilled

It gives a brief overview of many concurrency topics in Go, along with examples you can run in the browser. There's also a PDF version.

The book is AI-free.

antonz.org/go-concurrency…

Every time you write code in C, someone always has to comment, "look at the lengths people go to just to avoid Rust".

Like that's a bad thing.

Yes, I don't want to use Rust. I don't want to use Zig either.

I like C. Sure, it's wonderfully unsafe and ugly. It's ancient, too. I still choose to code in it.

I'll leave Rust to you safety fans.

Go's json/v2 brings MarshalWrite, MarshalEncode, MarshalJSONTo, MarshalFunc, MarshalToFunc, and, most importantly, MarshalMathers.

Well, maybe not the last one. But the others are quite real :)

You are much safer with Rust. You have plenty of time to think carefully about how safe your program is while it's compiling.

The Sqlean project (an extended function library for SQLite) started by collecting different SQLite extensions from around the internet, refactoring them into domain modules, and adding tests.

That worked pretty well — some people found Sqlean helpful in their work.

Unfortunately, this approach also caused a lot of bugs and inconsistent behavior across the extensions.

I saw three possible options:

— Leave the project in its current poor state.
— Spend a year fixing the code myself.
— Employ a clanker and be done in a week.

I chose the last one 😞