If you ever wanted to write a #QuickSetting or #LockScreen plugin for #phosh but didn't fancy #GObject C: Here's an example in #vala : https://gitlab.gnome.org/World/Phosh/phosh/-/merge_requests/1727

It's not that I'm a great fan of the #GObject type system and its way to build object-oriented code in C. I know some of the maintainers aren't as well, which I don't consider a surprise given the age and origin of that GObject ecosystem. So I absolutely understand #Canonical considered switching to #Qt for #Unity8, now #Lomiri.

But that's only one part of the story. The other part is I'm now using #GTK based desktop environments almost full time (only some occasions I turn on my old Mac).

static void xmpp_new_contact(XmppConnection *self, int n, ... ) {
    va_list args;
    va_start(args, n);
    for (int i = 0; i < n; i++) {
        buddy_t* buddy = va_arg(args, buddy_t* );
        g_log(G_LOG_DOMAIN, G_LOG_LEVEL_MESSAGE, "Contact: %s", buddy->jid);
    } 
    va_end(args);
} 

okay, i think i don't entirely understand when i should claim a reference using g_object_ref and when i shouldn't #GLib #GObject

question 1: should a function that returns a pointer to an object g_object_ref it for the caller's sake?

I have not blogged or talked about the follow-up work to my "GType Next" blog post that I've been doing in my spare time, mainly because it is happening *in my spare time*, and I don't want to give false impressions to people; the other reason is that the time consuming bit is not writing a bunch of code, but it's planning ahead, because the goal is to avoid breaking stuff at all costs…

i still dislike the way you have to write a lot of boilerplate code every time you want to write a new class in #GObject, but given that it's basically an OOP framework bolted on top of C, i understand why

i tried using #Vala to solve the problem, but encountered different, less solvable problems there

either way, things go on, now i'm trying to figure out how signals work

#RayLib + #Vala bindings + #OOP #GObject wrapper library written in #Vala = the *best* #gamedev experience of all time!!??
Well, we are working on it! :D At least @halfmexican is one of them!
Check out the vapi and WIP wrapper library, for example look at this beautiful `RaylibOOP.Color` class: https://github.com/Charadon/raylib-vapi/blob/main/src/lib/Color.vala
Also this library can of course be used by *all* other GObject language bindings.
And this sample is just the first, more are coming! For direct updates join our discord server!

Write your own Wayland Desktop!
The "Astal" framework, which is written in Vala, makes it super-simple! (you can use it with any gobject-introspection language though)
https://aylur.github.io/astal/
Here a WIP project from our community. So far a custom status bar, quick settings, MPRIS, etc. Together with the Hyprland window manager. Built with #GTK4, #Blueprint, #Libadwaita and of course #Vala!
https://github.com/ARKye03/morghulis

The simplicity of #UNIX has healed me from using #Java. Looks like these days I'd rather write a #C tool (or even use #GObject) than use Java tools again.
(I still like #Java as a language, but the #toolchain is incomprehensible.)