Ayke

@marcan@treehouse.systems as a maintainer, I prefer separate commits for separate things. But I also understand it's not always practical and asking for a change is not always worth burdening the contributor. So instead, I might say "alright, this one is fine but I'd prefer this other way next time". It's not a dealbreaker if that commit isn't perfect.

Also, I make sure everything is mechanically formatted and if it isn't, CI fails. It's just not worth having discussions about.

Clang/LLVM now supports small chips like the attiny10! They are even more limited than regular AVR chips and use half the registers for example, but with https://reviews.llvm.org/D131867 merged it won't (usually) generate incorrect instructions.

If you don't know, the attiny10 has 1kB program storage, 32 bytes (!) of RAM, and is about the size of a grain of rice. It has only 3-4 GPIO pins.

More information:
https://github.com/llvm/llvm-project/issues/53459

@alyssa@treehouse.systems oooh I should try this! I'm used to formatting on save, but formatting basically all the time sounds interesting!
(That said, I'm saving so often it might not matter)

@alyssa@treehouse.systems @chrispickard@hachyderm.io this is typical for Go, for example with the Go extension for VS Code (it's enabled by default). Not sure about other languages.

Having it included in the IDE is incredibly useful. For example: you paste some code and instead of indenting it manually just save the file and it's correctly indented. And if it doesn't, you know you have a syntax error 🙃
It also means you never forget to run the formatter because you don't need to.

Working on a precise GC for @TinyGo@mastodon.social! This means that the GC won't just blindly treat everything that looks like a pointer as if it is a pointer, but instead knows which part of an allocated object are pointers and which aren't (for example, ints and floats). This reduces false positives, meaning it won't accidentally keep objects around that aren't referenced anymore which reduces RAM usage. It could also result in performance benefits when correctly implemented.

https://github.com/tinygo-org/tinygo/pull/3346

@aissen@octodon.social I don't have control over the APs unfortunately. I could try to convince my landlord though.
It just feels like something that NetworkManager should support yet it doesn't.

Poor man's WiFi/BT coexistence on @AsahiLinux@social.treehouse.systems: pause a video to let it buffer the next minute or so, disable WiFi, and play without interruptions on the Bluetooth speaker. Repeat when hitting the "loading" screen again.
That is, until you somehow end up on a 5GHz WiFi connection and all stuttering is gone.