Walblumenhimmel?

There should be a menu-button with which you can open the inventory:

KDE Discover and GNOME Software can install from FlatHub (or other Flatpak repos, if you add those).

Yeah, so much of it is a mediocre/old joke overlayed on a generated image.

I’m guessing, there’s people out there, who genuinely just flood social media with these mediocre posts to try to grow accounts or similar…

Hmm, not sure, if I’ve heard of it. I’m guessing, we’re not talking about simply drawing a UML class diagram…? Is it for figuring out which object will have to clean up which other objects, in non-GCed languages?

Wundert mich, dass sie nicht gleich einen vollwertigen Grünstreifen anlegen. Da würden sich auch Bestäuber wohlfühlen, und so mancher Vogel würde im Frühjahr dort ein Nest bauen und dann im Sommer Schädlinge wegsnacken…

As far as I’m aware, the microfiber cloths specifically made for dusting have a structure like this:

So, it isn’t (intentionally) rough either. You wouldn’t really scrub with these. But yeah, certainly not ever going to be silky smooth either…

To me, it feels almost like I’m touching very fine-grained sandpaper…

Is that usable for dusting then, or is that for something else? I feel like for dusting, you want a somewhat rougher structure, so it can hold the dust better…

Dry skin is mostly caused by not enough oils being on your skin, which normally prevent the water from escaping. You’ll have a hard time hydrating so much that that’s no problem at all.

But at the same time, the cheapest lotion will do the trick. In principle, you can even use sunflower oil or similar. The water isn’t picky from what oil it gets blocked…

Personally, I don’t trust anchor links to continue working forever either. Well, and sometimes they don’t work, even when folks open the link fairly immediately (but do then work, when pasted into the URL bar a second time, which I’m guessing happens when the page takes a long time to load the actual content.)

So what I do, is that I always describe the info that I link, as if I was only linking to the whole webpage. That it does take you to the appropriate section of the webpage, is only for added convenience.

Das sind ernsthaft zwei Ortsteile, Bösgesäß und Böß-Gesäß…

Mine does a singular *ding*, which is very appreciated.

The last one seems to be mostly like Brainfuck, just with different capitalizations of “moo”: https://esolangs.org/wiki/COW

Yeah, these become a lot less relevant with routine.

• Avoiding the main-thread panicking is mostly just a matter of not using .unwrap() and .expect().

• String vs. &str can mostly be solved by generally using owned datatypes (String) for storing in structs and using references (&str) for passing into function parameters. It does still happen that you forget the & at times, but that’s then trivial to solve (by just adding the &).

• “temporary value dropped while borrowed” can generally be avoided by not passing references outside of your scope/function. You want to pass the owned value outside. Clone, if you have to.

• “missing lifetime specifier” is also largely solved by not storing references in structs.

The thing with OOP, particularly how it’s used in GCed languages, is that it’s all about handing references out to wherever and then dealing with the complexity of not knowing who has access to your fields via getters & setters, or by cloning memory whenever it’s modified in asynchronous code.

Rust has quite the opposite mindset. It’s all about tracking where references go. It pushes your code to be very tree-shaped, i.e. references typically¹ only exist between a function and the functions it calls underneath. This is what allows asynchronous code to be safe in Rust, and I would also argue that the tree shape makes code easier to understand, too.

But yeah, some of the patterns you might know from OOP will not work in Rust for that reason. You will likely need to get into a different mindset over time.

Also just in case: We are talking OOP in the sense of the paradigm, i.e. object-oriented.
Just using objects, i.e. data with associated functions/methods, that works completely normal in Rust.

¹) If you genuinely need references that reach outside the tree shape, which is mostly going to be the case, if you work with multiple threads, then you can do so by wrapping your data structures in Arc<Mutex<_>> or similar. But yeah, when learning, you should try to solve your problems without these. Most programs don’t need them.

Yeah, we onboarded some folks into a Rust project last year and a few months in, they were genuinely surprised when I told them that unwrapping is pretty bad. Granted, they probably did read about it at some point and just forgot, but that isn’t helped by lots of code using .unwrap() either.

Can still use .is_positive(), though…

What the heck, I thought you were saying you don’t want porn games. Flipping the letters like that is a common way of censoring. I was already somewhat confused, since I’m not sure, I’ve ever seen a porn puzzle game.

Hmm, I’m not getting a compatibility warning on F-Droid. I’m on Android 15, are you already on 16 maybe?