Here's the actual source from the parliament, https://www.parlament.gv.at/aktuelles/pk/jahr_2025/pk0643 (in German, but should be easy enough to translate).
They haven't said how they want to accomplish it, but some form of spy/malware is probably the only way. There is a lot of opposition to it (like https://www.parlament.gv.at/dokument/XXVIII/I/166/fnameorig_...) but unfortunately the terrorists have already won, so now everyone has neither freedom nor safety.
Can only hope this gets struck down by the constitutional court.
Are the SDKs AI generated? I looked at the Crystal, Ruby, and Zig ones and all they contain is a hello world example with some docs that have little to do with the code.
Sorry if this comment seems rude, just curious.
I've been trying Gleam of and on for a few years and different tasks. When it works it's really neat, but I find myself constantly having to write your code in Erlang which kind of defeats the joy of using it.
The biggest missing feature for me though is the lack of a receive syntax. Sending and receiving messages should be a first class citizen on the BEAM.
There is a very limited workaround in the standard library, but I guess the requirement for type safety means we'll have to wait forever for anything that can actually do things like listen to PIDs or the inbox without Erlang or if the box.
I'm still hopeful this will be tackled, as I really can't stand the concurrency primitives of most other statically typed languages and Gleam has the most promise to fill that niche.
> The primary motivator for Firefly's development was the ability to compile Elixir applications that could target WebAssembly, enabling use of Elixir as a language for frontend development. It is also possible to use Firefly to target other platforms as well, by producing self-contained executables on platforms such as x86.
We're only using CUE in a very limited fashion now, mostly went back to writing everything in Nix to keep things consistent. Learning Nix is already quite a hurdle without also forcing people to dive into CUE.
I originally introduced CUE at IOG to provide a sane alternative to HCL that doesn't involve setting up a Nix environment, but the lack of functions and ways to abstract much, abs the bed to keep our CUE schema synced with the Hashicorp code ended up curbing a lot of enthusiasm.
I'm looking forward to using Nickel for this niche in the future when it has better interop with Nix and maybe some way of handling user input.
For Steam, NixOS actually builds a full FHS with all the packages from SteamOS and then runs Steam within that using a simple chroot.
It works surprisingly well and can also be used for stubborn software that cannot work without FHS and without messing up the rest of your system.
scrolling in Firefox on Android is really unpredictable and hard on this site. it seems like a nice idea, but I couldn't get past the first few choices.