It is definitely an improvement over Java Swing. One thing I really love and miss with other frameworks is how easy it is to connect properties with each other. All values are exposed as Properties and Values. Values can be listened to, mapped and used. They are similar to RXJS’s Observables except that you can always get the internal value without a lastValueFrom that may fail. Properties can also be listened to, mapped, etc but their value can also be set from everywhere (RXJS instead has Subjects which can only be set from inside the constructor). It’s a really easy, yet powerfull system. I have yet to find a single framework that does that part as well as it does.

And regarding Rust lack of stable ABI, even if that’s resolved (and last time I checked there wasn’t much interest from within). The main Linux distributions will still have to ship the Rust stdlib as a shared library to be able to reliably depend on it being available.

I do wonder if it would be advantageous to write a safe wrapper around the C and C++ standard libraries. It would mean being able to use it’s functionality, while being relatively sure that those dependencies are available while only having to add a little extra code (and thus size) to the executable for the wrappers.

Yeah, I wrote two “plugins” some time ago and the Assembly implementation was shorter than the Rust implementation due to the need to convert from C ABI and back 😅.

I have taken a look at both Slint and Egui before, but they didn’t seem to integrate that well with the Linux desktop last time. I just checked again and it seems like Slint has a Qt backend now which is nice. I don’t really like immediate GUI frameworks, but JavaFX has so far been my favorite framework to work with so maybe I’m just weird.

And yes, I have used min-sized-rust’s tricks for several of my projects, and it’s very effective. However statically compiling just doesn’t compare to using C and linking with the system libraries.

I wrote a GTK application in Rust some time ago and it was filled with macros to deal with lifetime issues. Most issues could only be solved with unsafe macros or Rc<RefCell<T>>. The experience working with it is probably a lot better when using newer declarative frameworks, but using it with a toolkit written for C wasn’t fun.

I personally prefer it for cli programs. The executables are considerably larger than C programs due to static linking, but that does mean that it works regardless of what libraries you have installed without any hassle.

That looks really interesting, thanks for sharing

Yes, it does have a lot of similarities.

He does that to strongarm companies into complying, because it works. It’s also setting an example for other countries to cooperate.

1. Follow the 3 - 2 - 1 backup rule.
2. You can use SMART to see the health of your drive.

Neat tool

I’ve seen some programs put their shit in ~/Documents which is even worse.

You should be able to set a watch using the Linux Audit system (which home-watcher also uses). Try something like this

sudo auditctl -w /.Trash-1000 -p rwxa -k trash_monitor

You should then be able to search for events in the logs with

sudo ausearch -k trash_monitor

This is completely absurd, why would they want to make the straws last longer?

MySQL wouldn’t win any single event, but would get high scores all around for unknown reasons.

There are a lot of companies running XAMP / LAMP stacks, for some reason.

MongoDB would be at the front desk trying to convince the judges to let it enter, and while doing that would accidentally drop a suitcase filled with business and government secrets.

But haven’t you heard? It’s webscale!

And MariaDB was named after his second daughter right?

It was to be expected but I didn’t think it would be public this soon

Is there a way to export them with Markdown to prevent missing arms?

It’s a joke about the criticism systemd gets

Is Wikipedia also protected under Article 5?