home.social

Andreas Bergmeier :rust:

@[email protected]
View on fosstodon.org →
  1. Andreas Bergmeier :rust: @abergmeier ·

    Both and implement Flowgraphs with GTK.
    Neither of them are usable for my App. Thus I probably need to implement a third Flowgraph library in , which again - will not be usable by anyone else.

    #helvum #libgtkflow #golang
  2. Andreas Bergmeier :rust: @abergmeier ·

    Am I doing it wrong or is dbus_interface in basically forcing me to leak references?
    Tried structs with lifetimes but it seems like dbus_interface always forces the struct field lifetime to 'static.

    #zbus
  3. Andreas Bergmeier :rust: @abergmeier ·

    @rhgrouls @sanchayan Day 2 of using . A lot to like - but some shortcomings.
    Hope they are open to extend the current functionality.

    #gitui
  4. Andreas Bergmeier :rust: @abergmeier ·

    seems amazing. Will give it a shot.
    For years now I have been using git-gui. Since tcl does not integrate great with my Desktop, pure terminal solution might work better.
    Extending git-gui with their obscure language never seemed possible. With rust sky might be the limit.

    RT @rhgrouls
    "lately, I have been using gitui, built in . I set up a toggleterm + gitui keymap in , but I also like to use it outside of neovim. github.com/extrawurst/gitui"

    CC @sanchayan

    #gitui #rust #neovim
  5. Andreas Bergmeier 🍵🪵 @[email protected] ·

    @train I know it is useful for ~3 things.
    1. Defining quirks for ALSA
    2. Defining quirks for Hid/++
    3. Exposing highly semantic interfaces to userspace.

    For these former two, #ePBF brings benefits by allowing userspace to quickly iterate over necessary fixes. Also there is a good chance you can then backport fixes easily to LTS.
    For the latter exposing interfaces via ioctl or sysfs is cumbersome in highly semantic scenarios. Here #eBPF could make sense as long as latency, etc. is not a concern.

    #epbf #ebpf
  6. Andreas Bergmeier 🍵🪵 @[email protected] ·

    @dragnucs Difficult and embarassing topic.
    I wrote prototypes for Terraform Providers for #podman, #buildah and #kaniko IIRC.
    ALL of them are horrible at caching layers - let alone remote exec.
    The only descend approach which supports caching seems to be #buildx + #buildkit. And yes, I have a prototype implementation for that as well.
    We are still not testing this though, since hosting a Buildkit Remote Builder on GKE is a nightmare.
    Let alone error handling in both buildx and buildkit is BAD.

    #podman #buildah #kaniko #buildx #buildkit