Antonz

Everyone is creating a new programming language these days, often one that's "like Go but with more features" or "like Rust but simpler". Solod, a systems language for C and Go developers, might look like one of those languages, but it takes a different a

Go's standard library has a slices package with a function called Backward. It lets you iterate over the elements of a slice in reverse order: // Backward returns an iterator over index-value pairs in the slice, // traversing it backward with descending i

Solod (So) is a subset of Go that translates to regular C - with zero runtime, manual memory management, and source-level interop. It's designed for two main audiences: Go developers who want low-level control without having to learn another language. C d

Interactive book on concurrent programming with auto-tested exercises.

Over the past two years, I've published interactive tours for five Go releases, from 1.22 to 1.26. I know some of you have read them, and I've received a lot of kind words from you (even some core Go team members reached out) - thank you so much for that!

Go's concurrency is one of the main reasons people like the language. You write go f(), send values through channels, and the runtime scheduler runs thousands of goroutines on just a few OS threads. It feels effortless. None of that machinery exists in C.

Solod (So) is a subset of Go that translates to regular C - with zero runtime, manual memory management, and source-level interop. It's designed for two main audiences: Go developers who want low-level control without having to learn another language. C d

Solod (So) is a subset of Go that translates to regular C - with zero runtime, manual memory management, and source-level interop. It's designed for two main audiences: Go developers who want low-level control without having to learn another language. C d

Creating a subset of Go that translates to C was never my end goal. I liked writing C code with Go, but without the standard library it felt pretty limited. So, the next logical step was to port Go's stdlib to C. Of course, this isn't something I could do

Creating a subset of Go that translates to C was never my end goal. I liked writing C code with Go, but without the standard library it felt pretty limited. So, the next logical step was to port Go's stdlib to C. Of course, this isn't something I could do