Leaflet @ that_leaflet @lemmy.world

[Mastodon](https://fosstodon.org/@that_leaflet)

---

Read more

Posts

261

Comments

373

Joined

2 yr. ago

Android uses forked versions of the Linux kernel, based on Linux LTS versions. They added in Rust support in 2019 and most new code since then has been written in Rust in order to avoid memory safety vulnerabilities. And memory safety vulnerabilities have been significantly down since 2019.

Now that upstream Linux is adopting Rust, we should hopefully see a similar results. Though likely slower than Google (they went all-in on Rust) while upstream Linux new code will seemingly be mainly C for the foreseeable future.

Note that this is from late July.

I think that’s just a dependency issue unrelated to the script.

I have a bash script I use to script my Silverblue install. Something like this should work.

    
# space-separated list of packages to install
S_RPM_PACKAGES_TO_INSTALL="pkg1 pkg2 pkg3"

# function to install the packages
dnf_install () {
    sudo dnf install -y $1
}

# call to function, passing the list
dnf_install "$S_RPM_PACKAGES_TO_INSTALL"

  

I have it set up this way so that I just have a bunch of bash variables describing the stuff I want to install all at the top of the file, but the function definitions and calls lower down since I don't need to see them.

It also does other things like removes packages from the system, removes some preinstalled flatpaks, installs flatpaks from Fedora Flatpaks / Flathub / gnome-nightly, and sets up gnome through a list gsettings commands.

As I use my system, I add new apps to the list I want next time I install and remove apps I don't use.

I doubt this will have much of an effect. Compositors already implement protocols that aren’t in upstream yet.

All this really is is putting some of those protocols in a GitHub repo and giving them a nice name. Gamescope will naturally implement them because frog works on gamescope. KDE might implement a few. Gnome and wlroots probably won’t implement them because (1) Gnome prefers a more lean set of protocols and likely won’t adopt a protocol until it’s “finished” and (2) Simon Ser, the wlroots main maintainer, is very involved with upstream protocols and would rather see development happen there.

Worked on Flathub Firefox for me.

Fedora 41 is shipping the 2.99 version. And naturally will update to RC1 and later once they release.

There’s non-destructive editing in 2.99. Not everything is non-destructive though, such as rotating and scaling. But most colors and filters are.

Flatpak doesn’t care about your ports, they can access them if they have network permission.

I see that too on the top level in the hierarchy.

This GitHub comment has the command to give Steam the permission it needs for VR.

https://github.com/flathub/com.valvesoftware.Steam/issues/898#issue-1222145279

Not out of the box, but you can make it work.

home/some-dir takes precedence.

More specific rules overrule general rules.

Debian 12 with Gnome uses pipewire for audio.

I use the Steam flatpak. The nice thing about that is that 32bit libraries aren’t installed on the host system.

The most important thing for apps to do for speedups is to use LZO compression and modern runtimes.

The Firefox snap did some Firefox specific optimizations, especially around its language packs, to speed things up.

Rust developers are fine with C bindings changing, they just want that to be communicated to them by the C developers before they break.

Do keep in mind that Ventoy works differently from flashing tools like BalenaEtcher. Those differences may break certain ISOs, though in my experience that's rare.

I used to update my laptop in class because my school's WiFi was so much faster than my home internet.

That's really strange, the new renderer has been tested pretty thoroughly with modern Nvidia; issues are only expected with older Nvidia cards that require older Nvidia driver versions.