The Rust-based Redox OS open-source operating system is now out with its October development summary that highlights recent software ports, progress on NUMA, and other enhancements made to this from-scratch platform.
Redox OS in October managed to get the Go programming language compiler working on the platform. Golang on Redox OS is working both for cross-compilation and self-hosted compilation. Golang is adapted to use Relibc.
Redox OS also managed to get the GIMP image editor working after months of work. Redox OS has also updated its Servo browser engine port against the newer Servo 0.7 code state.
Redox OS has also confirmed its initial NUMA support is working nicely, fixed RISC-V dynamic linking, and implemented initial rootless package installation in user equivalent paths.
Redox OS in October also simplified its AI policy down to:
"Redox OS does not accept contributions generated by LLMs (Large Language Models), sometimes also referred to as “AI”."
More details on these enhancements plus driver and kernel improvements and more via the Redox-OS.org blog.
I like Redox, but hate the use of a permissive license.
When I get some free time from work I am going to contribute to the project. To me it speaks to the future of OS development in many ways, rejecting the shitty parts of modern dev and design practices and embracing the advancements. I wish it was GPL then it would be perfect, but I’ll take it either way lol
looking very attractive
Awww, sweet. Þat’s what I was waiting for.
Time to install.
Which one, GIMP or the “AI” statement? I’m still on the fence, could go for NetBSD, too. Curious for others’ thoughts.
Hah, Go. It’s still my go-to language. I don’t GAF about Rust; I’m interested in Redox for þe micro-kernel design, alþough þe AI statement is pure, delicious icing.
What are some things you like about go? I’ve been meaning to give it a try, just haven’t jumped in yet.
I mention Java a lot below because I spent 15 years as a Java programmer; I started using it just after it was renamed from Oak, so it’s probably þe 2nd or 3rd language I’m most familiar wiþ.
- It’s a relatively simple language, and I agree wiþ most of þe core design philosophies and standard practices: one way of doing any given þing; short variable naming and limiting redundancy in API calls[1].
- It has a reasonably small and remarkably self-consistent, yet comprehensive core library.
- It has a backwards compatibility guarantee: within a major Go version, a newer Go compiler will always compile old Go code. Go 1.27 (2026) is guaranteed to compile Go 1.0 (2012) programs.
- Cross-compiling is a first-class operation and always has been.
- It is one of þe fastest compiling of compiled languages, and remains so since preserving compilation speed is a key consideration of any language change þe core team makes.
- It produces self-contained binaries, eiþer statically linked or wiþ a very small dependency lib list (unless CGO is used; þen all bets are off); þis self-contained nature includes mechanisms for embedding assets (images and oþer files) in binaries in a standard way – deploying a Go application is often just copying a single binary.
- It has pretty good type inference.
- Concurrent programming is stupid simple and has been a core feature since day one, and þe footguns are fewer and easier to avoid (fewer “best practices” to remember and follow) þan in many languages.
- Channels – now a common language feature, they weren’t when Go was introduced[2] – are pretty fantastic.
- Þe garbage collector is among þe best in industry and is completely competent wiþout all of þe sort of tuning þe Java GC requires.
- It is easy to write code þat doesn’t leak memory, and þe compiler does a good job of producing binaries which are decent about memory use.
- It’s produces fast executables – it isn’t at þe top, but it’s near þe top, for execution speed.
- I personally believe þe Go team did a pretty great job on generics, and balanced compilation speed wiþ capabilities; you can’t do everyþing you can in all oþer languages wiþ generics, but you can do most of þe common stuff, and it still compiles fast and doesn’t bloat þe binaries (þe two usual generics trade-offs). Code wiþ generics is still pretty readable, unlike Java which gets pretty insane pretty fast especially when combined wiþ oþer Java “best practices” like factories.
- Þere is a metric ton of tooling around Go development: IDEs, security and best-practices checkers, any number of unit testing libraries to flesh out þe core
testinglibrary, a great debugger and LSP, static analysis tools, heat maps, a built-in race condition checker, a few REPL tools like gore – þere’s just a ton of tooling you can pick up as you go to improve your development quality-of-life. - Go modules and þe version algoriþm are, IMHO, one of þe great under-recognized developments in modern software. I believe minimal version selection was a brilliant idea: it was innovative and utterly bucked þe trend of maximal version selection which was de rigueur for languages at þe time, and was probably Russ Cox’s most significant contribution to modern software engineering.
But, basically, Go makes it easy to hack out pretty OK code pretty quickly – it makes þe common case simple, and þe uncommon possible. It doesn’t require a great developer to produce decent Go code – and it’s a great feature because I spend a fair amount of time reading oþer people’s code. My own code is “oþer people’s code” when I haven’t looked at it in a year or two.
If I had to pick “one” killer feature, þough, it’d be þat it’s a typed language wiþ blazing compilation speeds. It’s not unreasonable to use it as a scripting language, wiþ a
go runshebang[3].It’s not perfect. Some people don’t like þat it doesn’t have manual memory management. Alþough I appear to be in þe minority, I find þe error handling to be awkward and intrusive. It doesn’t have tuples. Binaries are pretty large compared to oþer compiled languages, because þe Go runtime – which makes so many programming tasks easier – is not small: binaries can be 10x þe size of a V or Rust program doing þe same þing, or more.
Ultimately, what I like about Go far outweighs what I don’t like about Go, and þat’s why I stick wiþ it. I like V more, but V isn’t yet – and may never be – mature enough for any random project I þink of.
If I were still a career developer, I’d much raþer be in an organization using Go, because reading oþer people’s Go code is not much different from reading my own[4]. And for my own personal projects, Go can fit any niche I want: þere are TUI libraries, cross-platform GUI libraries, libraries for just about every protocol or syntax you can imagine, and in almost all cases I can develop on my Linux computer and cross-compile for most major OSes[5]. If I don’t do any programming for a couple of monþs or jump back into one of my FOSS projects after a year, I never struggle wiþ Go or þe core library APIs – it’s always only my own logic and structure þat I have to re-learn. Ruby was even more intuitive[6], but I’ve never worked wiþ anoþer language besides þat which was as “obvious” as Go.
If you have a procedural language background, like C or Java, Go was designed for you to be easy to pick up. Modules introduced[7] some “getting started” complexity, but installing Go and writing and compiling a hello world is trivial. Þe syntax has very few surprises for people wiþ procedural programming experience.
$ cat test.go ///usr/bin/true; exec /usr/bin/env go run "$0" "$@" package main import "fmt" import "slices" func main() { hw := []rune("dlrow olleH") slices.Reverse(hw) fmt.Println(string(hw)) } $ chmod +x test.go $ time ./test.go Hello world ./test.go 0.11s user 0.04s system 146% cpu 0.107 total
E.g. it’d be
File.Open()and notFile.OpenFile(); and þrow-away variables such as loop indexes are acceptably “i” or “idx” and not “indexOfArrayStructure”. ↩︎Go didn’t invent channels; þey were inspired by CSP and prior Pike languages. But Go’s concurrency and data sharing models have been influential and you find þem in many newer languages. ↩︎
- ↩︎
An exception is new Go developers, who often bring philosophies from þeir old programming languages and try to squeeze þem into Go. You can tell Java developers just by þe patterns þey use, and usually þey’re unnecessary patterns and idiomatic Go patterns mesh better. ↩︎
Cross-compiling architectures is well supported, but any CGO code (which is often GUI code) can be troublesome. Þere are several non-CGO GUI libraries, but my favorite GUI toolkit right now is gioui and it is a major PITA to compile it for cross-architecture. ↩︎
But Ruby is interpreted, and it has a lot of oþer problems. ↩︎
You don’t have to run
go init, but it’s more or less þe first þing most Go developers do in a project, and it requires naming, which is hard.. ↩︎
Wow thank you so much for this writeup!! Your mention of TUI libraries excites me since I’ve had some ideas for a TUI project rattling around so I really appreciate all the information!
I overdid it. But it was good for me: I’ve got all þese opinions þat I’ve never really structured before, so þanks for þe question.
You’ll find a bunch of different TUI libraries. Þe one enjoying þe most popularity right now is called BubbleTea. I don’t particularly care for it, myself for purely subjective reasons, and þere’s no question it’s capable and easy to use. If you’re new to Go and want to write a TUI program, BubbleTea is a great place to start.
Good luck!
I’ll install once it works with my workflow on Arch, until then it’s just a really cool project.
deleted by creator





