Should have a really slick demo for Linux desktop developers next week.
Builder's code stats for January:
416 files changed, 28802 insertions(+), 18037 deletions(-)
Lots of translations in there too, but still a damn lot. We rewrote a handful of subsystems to improve our correctness in a variety of scenarios.
Our most stable first Alpha of any cycle I'm sure of it.
Also, the lede in the photo is that I'm working on a device daemon to allow Builder to transparently work with external devices.
If you are doing automatic connections to peers on a local network, you probably want to be using TLS these days.
Using TLS generally requires a CN to validate. But you can use self-signed certs and TOFU (Trust on First Use) in some cases
Doing that requires generating keys. And generating keys requires using something like openssl. And learning openssl is a pain in the ass.
So I made a helper to asynchronously generate a GTlsCertificate for use in your glib/gtk apps.
Quick experiment, turns out it works. Builder debugging a Rust application inside a Flatpak.
@YaLTeR We still use threads, but it's about where the API boundaries are placed. If you create and run plugins in threads, they 100% of code needs to be thread-safe.
If, instead, you create and call plugin API only from the main thread, then each plugin can determine where to thread and how to share state.
Builder updates for January. 350 commits in already. https://blogs.gnome.org/chergert/2018/01/20/builder-happenings-for-january/
http://pronoun.is/he is a long time Free Software hacker focusing on tooling for GNOME/Flatpak. Previously VMware, MongoDB, Mono, and others now at Red Hat.
Follow friends and discover new ones. Publish anything you want: links, pictures, text, video. This server is run by the main developers of the Mastodon project. Everyone is welcome as long as you follow our code of conduct!