2xsaiko

It's very unlikely there's a GUI tool that will do this unless you write one yourself, that sounds like a very uhhh, unique naming scheme. You can sort them using a shell script:

for file in *; do
  name="${file%.*}"
  suffix="${name: -2}"
  printf '%s\t%s\n' "$suffix" "$file"
done | sort

Alternatively, modify this so that it will create symlinks in a new folder that have names that will get sorted correctly in whatever GUI tool.

Ah, yeah openrc is nice and I used it for a long time with gentoo, but it does lack a lot of the useful features like this one.

server applications

Note that systemd can use most if not all of the isolation features nsjail lists in the readme already for services it manages.

I love them! Great work!

It would need some sort of way to hook into the compositor. PowerToys has it easy because they can just add the necessary APIs to the Windows compositor if it doesn't already have them. And I feel like compositors would just implement it directly instead of designing an API for it because that's less complex.

Rewriting huge parts of the IDL compiler for Nucom, my implementation of Microsoft’s COM binary interface standard and (in the future) network protocol. The original version was hacked together with a lot of assumptions made in the parser and isn’t very extensible, and I do need to extend it now.

(Nucom is another way to have a stable ABI for Rust, e.g. for a plugin interface, and for Rust/C++ (and more OOP-style C) interop, based on objects with vtable pointers. And hopefully sometime in the future, transparent IPC and networking so you don’t have to load plugins into your process’s memory space if they don’t need to be there, with it working the same as if it were direct calls. All of this I assume you can already do on Windows with the windows-rs crate but it's obviously Windows-only.)

I do have to say though, I need a better way of transforming my syntax tree. Right now I’m just copying the struct definitions over and over for each compile stage and manually writing code to copy everything instead of just the parts I’m actually transforming, and it just seems like there has to be a better way. I might want another proc macro for this.

Someone else who has the Omnia! I agree, it’s a great router.

Please report this on https://bugs.kde.org/. I can't find a bug that looks like the same issue at least.

Traits like std::io::Write are essentially Strategy pattern. Take a look at how that’s used. You’re doing it mostly how I would, except for the Box. Generally it’s preferred to use generic functions/types in Rust instead of dynamic dispatch, i.e. have a fn do_something<T: MyTrait>(imp: T) instead of a fn do_something(imp: &dyn MyTrait).

They’re FIDO keys but bad.

Here’s a great blog post from someone who knows what they’re talking about: https://fy.blackhats.net.au/blog/2024-04-26-passkeys-a-shattered-dream/

Oooh, saving this for potential D&D games or other storytelling purposes. Thanks!