Programming Leftovers
-
Go 1.21 Release Candidate
The Go 1.21 first Release Candidate (RC) is available today on the download page! Go 1.21 is packed with new features and improvements. Getting the RC (release candidate) allows you to experiment with it early, try it on your workloads, and report any issues before the final release (scheduled for August). Here are some notable changes and features in Go 1.21; for the full list, refer to the full release notes.
-
Kernel 5.15.117 compiled with 9P features for QEMU
The "9P" requirement was discussed in this blog post a couple of days ago:
https://bkhome.org/news/202306/qemu-recompiled-in-oe-with-more-features.html
The "9P" enhancements required in the kernel are explained here:
https://wiki.qemu.org/Documentation/9psetup
I have compiled the Linux kernel version 5.15.117, with these new features
-
Agile is people, the rest is commentary.
You may have heard of this new idea called “Agile”, where you prioritize people over processes etc etc etc. I occasionally saw it on Twitter, before I quit that hellsite, after which I kinda lost track of it.
-
Synchronization in Vulkan
An important part of working with Vulkan and other modern explicit rendering APIs is the synchronization of GPU/GPU and CPU/GPU workloads. In this article we will learn about what Vulkan needs us to synchronize and how to achieve it. We will talk about two high-level parts of the synchronization domain that we, as application and library developers, are responsible for: [...]
-
Review use of Qt module header includes
Having come across sources using include statements for some Qt module headers (like
#include <QtDBus>
), memories arose about a check from the static analyzer tool krazy as once run conveniently on KDE's former ebn.kde.org site. That check, called includes, poked one not to use Qt module headers. Due to resulting in the inclusion of all the headers of those modules, and then again that of the other Qt modules used by the module. Which them meant more stuff to process by the compiler for compilation units with such module header includes.So is that perhaps in 2023 no longer a real-world noticeable issue? A first look at some preprocessor outputs (with Qt5) for a single line file with just an include statement hinted though it might still be true: [...]
-
This Week In Rust: This Week in Rust 500
Hello and welcome to another issue of This Week in Rust!