snaggen

Well, there is also a more right leaning take. You take care of your self and scratch your own itch, and you should not be a liability to the society, but make your self useful and contribute back. And I think this is kind of the reason FLOSS works well, it can be aligned with many philosophies.

I noticed that the Flatpak didn't work on Fedora 39, probably due to how they build the flatpak or something. I had no problem taking screenshots under Fedora 39 Wayland session using the Appimage.

Flameshot has wayland support, however there seems to be some issues that might need to be worked around. Like https://github.com/flameshot-org/flameshot/issues/3326#issuecomment-1854902229

If I look at what I use and what annoys me, I would have like to see focus on 'Dyn async trait' and 'Traits for being generic over runtimes'. I think it is quite annoying that you have to decide on a whole eco-system when you are doing async code. I have had times when I have search for a very niched library, only to find that it is written for the wrong async runtime. And the longer it takes to correct this, the more cemented it will be.

Tested to search for a stomp rust crate and got horrible results. So, I guess that you should test the different search engines with your use case and see which one fits that.

My company actually used a whiteboard instead of a DNS for our internal network. We used it as a temp solution during setup, then 5 years later it was still in use. It worked quite well.

Have you tried to run it as root?

If there just were some link, to some blog post or something, that would expand on the topic.... with a tl;dr for the really lazy people... well, that would have been nice....

I see this post as an advice to learn gradually, and to write sloppy but painless code initially. Then when you have the basics, you can add the more idiomatic and tricky parts.

Well, you don't need it until you suddenly do. But I guess it might be very different for different users depending on your use case. I have found myself needing to go low level for async a few times, and I don't think I'm doing very strange things.

Well, when you write async code, you may suddenly find your self needing to implement AsynRead or something similar. Suddenly you have to use pin, and understand how async worksbunder the hood. So, while I agree that async is not something fancy, it will possibly throw you in some quite advanced territory. The part I'm not sure I agree with is skipping the error handling. But I see what the authors intention is, to keep hairy stuff out of the way while learning the basics.

But you are using characters you didn't invent to communicate this, without paying someone. Invent your own alphabet!