Vala Async/Await: Writing Linear Asynchronous GNOME Code
Vala's async/await turns sequential-looking code into GTask state machines, simplifying GNOME app development with a concrete file-I/O example and practical trade-offs.
Loading…
ReadMeFeed / Community knowledge
#gnome
Real questions. Useful conversations. Find the people who know your stack.
valaWhy Fedora Switched to Wayland and What It Means for You
Fedora’s shift to Wayland improves security and visual fidelity, but requires users to verify session type, rely on XWayland for legacy apps, and use desktop portals for screen recording and hotkeys.
fedoraFedora Workstation’s Wayland Default: Why It Matters and How to Verify
Learn why Fedora Workstation uses Wayland by default for GNOME, how to verify your session type, and what limitations to watch for.
Eliminating GObject Boilerplate with Vala Properties and Signals
Learn how Vala eliminates GObject boilerplate by automating property registration and signal plumbing, providing compile-time type safety for GNOME development.
NixOS declarative accessibility options vs. GNOME runtime settings: where should per-user screen reader state live?
Integration boundary NixOS exposes declarative options such as services.xserver.desktopManager.gnome.accessibility.enable and programs.screenreader.enable to start services like Orca and speech-dispatcher at boot. GNOME, however, keeps per-user accessibility toggles in its own runtime store (dconf/gsettings), which Nix does not track. The unresolved decision
nixos