A tool to estimate how powerful a gaming PC you can build depending on your budget.
Complicated.
A Kubernetes admission control endpoint. Easy to deploy and configure.
I use it for mutating admission control in order to patch resources deployed by Helm charts or operators.
Container-based CI.
Kotlin Multiplatform app navigation and architecture framework for declarative UI that works well with MVIKotlin.
Model–View–Intent for Kotlin Multiplatform. Works well with Jetpack Compose and Compose for Desktop. Supports time-travel debugging.
In asynchronous code, Swift provides access to single-shot continuations. I wonder what fun trickery one could perform by abusing this.
Podcasts, articles, and tutorials on Swift and SwiftUI.
A popular tutorial that teaches Swift, SwiftUI, and mobile app development in 1 hour a day, for 100 days.
A binary-to-text encoding optimized for UTF-16.
Detects unsafe Rust code.
Rust crate that fails compilation if your code can panic.
Rust crate that helps make your code unsafe.
Rust crate that casts any reference to 'static lifetime using only nominally safe code.
Rust crate that implements transmute using only nominally safe code.
One highlight that I am looking forward to watching the recording of is Matias Piipari: Canonical-distributed Deb and Snap packaging of the Swift toolchain for Linux. I’m curious what level of support there will be.
Related: The YouTube channel of the conference.
A Swift library for Swift code parsing and manipulation.
At present Foundation has an Objective-C core on Apple platforms and a C core on others. In the future there will be a unified Foundation implementation with more parts in pure Swift, which makes it more portable and easier to split into multiple independent parts.
Redux for Kotlin, and in particular Jetpack Compose (including Compose Multiplatform).
Swift web server framework.
Swift package GitHub crawler and indexer.
Lazy dynamic constants for Java. Implemented as dynamic constant pool entries.
Given that a significant part of the startup time of a typical Java application is taken up by class initialization, I wonder if this could be used for good effect when declaring the ubiquitous Logger instance and such.
A more verbose alternative that works without this is:
private static Logger logger() {
class Statics {
static final Logger logger = Logger.getLogger(Parent.class);
}
return Statics.logger;
}
As the Dycon README points out, this alternative (which is a variant of the initialization-on-demand holder idiom) incurs overhead in the form of an additional class object, so it has its drawbacks. Still, you may prefer it because it does not involve bytecode trickery.