> neither of those languages has dynamic linking

what do you mean by this?

Neither Go nor Rust define an ABI for themselves. They can use dynamically linked C code just fine but cannot link their own language with all (or even a reasonably broad subset) of its own features. This is not as bad in Rust, where you can fall back to the unsafe C ABI while still having safe Rust on either side, whereas Go cannot have two instances of its runtime active in the same process.

Compare this situation with Java/JVM or C#/.NET, both of which define their own ABIs albeit not for native machine code, or especially Swift, which defines its own native-code ABI.

you can totally still do this

I do this. My workflow is CLI only in Objective C. No Swift. No SwiftUI. No .xib files.

Very exciting stuff!

Remind me again why we can't use HTTPS certificates to sign code that is linked with a domain?

Only Linux, BSD and other operating systems that are entirely Open Source.

Even Windows has scary warnings now that pop up unless you pay several hundred dollars a year plus you have to go through a completely unreasonable process (that often requires being shipped a physical USB device) just to sign your application.

> require your device to be running an official rom signed by Google

How exactly does the app detect this?

Google play service integrity, before it was safety net.

Can’t be bypassed without root and otherwise all rom not official and validated by Google are on time watch.

https://android-developers.googleblog.com/2024/12/making-pla...

If only this was voluntary and automated by an Open Source service provider, so that I only have to pay one monthly fee and all the FOSS that is detected to be in-use on my machine is funded.

If the OSMF takes off, I could definitely see something like this taking off.

Go is a great language because it has distinct types by default, it's not about "making invalid states unrepresentable", it's about recording relationships about a particular type of value and where it can be used ie. it doesn't matter that UserID is just a string, what matters, is that now you can see what string values are UserIDs without making assumptions based on naming conventions.

Can you add support for duplex numbers? (duplexnumbers.com)

I'm unfamiliar. Are duplex numbers specifically used in quantum computing?

This is great! There's way too many arcane text file formats (configs, Dockerfiles, workflow definitions etc) without any sort of fast feedback loop on type-safety, documentation etc.

We need more projects like this and if a system is running SystemD, this needs to be enabled and integrated with any LSP-supported editors.

Thanks for the positive feedback! The documentation needs a bit of revision, but I agree there's a lot of configuration file formats that should be supported with language servers that might not necessarily have rich AST parsing as part of their contents.