That requires a complete picture and all possible use cases from the start. Initially when a language is new and hardly used there are much to benefit from flexibility and trying new concepts. Then as the language matures, a more formal process is needed to ensure stability. There is a reason these discussions comes now, since rust is in a very stable phase.

Which is kind of surprising, since it basically just is a bunch of "I'm cannot understand why .... is needed", "I cannot learn...." and "I think that is ugly". And since the OP is coming from TypeScript, and how the OPs understanding of programming, it is clear it is a junior web developer trying rust and failing. Nothing to see here... well, the OP clearly have some kind of grandios ego, thinking that the OPs inability to learn something, must be because it is bad (I mean, there is clearly no other possiblities)... but not even that is worth responding to. And don't read this wrong, there is plenty to complain about with Rust, however, nothing of that is in OP which is basically just as insightful as a baby crying.

https://firstdonoharm.dev/

I have been in this community from the start and seen it grow from nothing to almost 5000 members, so I think this community have done pretty good. We are one of the top communities on programming.dev.

I have tried to post news, blog posts and updates that I find interesting and relevant for others to read. And while that provides some content to the community, it gives the community a bit of a Rust News Outlet kind of feel. So, what is missing from this community is a feeling of being alive. The only way to do that is for people to start posting more informal posts, and at this point I think that we should be very generous about what to accept. Other communities like /r/rust might not allow memes, and self promotion is generally frowned upon. But at the point where this community is, I would be happy to see all kinds of content. So go ahead, Ask questions, Post about your projects (even if it might be a bit of self promotion), re-post that funny meme you have seen somewhere (as long as this doesn't turn in to a programmer humor place). Then if we get to the point were things starts to be problematic with a to loose attitude, we can address that when we get there. But that probably means we have gotten to the point were this place feels alive.

The borrow checker handles more than just freeing allocated memory, it will also prevent data races and invalid concurrent access aso. I personally don't have any issues with using garbage collected languages, but the fearless concurrency is nothing I'm willing to give up.

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.

Well, I agree. But what I mean is that when people ask physics questions, it is often implicitly understood to mean under current conditions. You rarely hear normal people or kids (who I find asks most of the physics question) include anything about frictionless vacuums in the question. (For reference: https://xkcd.com/669/ ). So, for the egg question, regular people would most likely consider the answer to be "No, except under very special circumstances". But, I agree with you that if a simple Yes/No answer is expected, it have to be Yes.

Well, of course you should stick to rustc if you don't need the certification. I get the impression you mix up thing and the purpose of a certified compiler.

Ferrous Systems is working on certifying a specific version of rustc, and hence make it possible to use rust for projects where such certification is required. And certification is required for things like programming medical equipment. If you are hooked in to life support, it is good if the compiler did the thing it was supposed to do.... a crash in such programs can be fatal in a very literal way.

Also, notice that they try to do this without forking and by contributing upstream.

I hope this means that it will be easier for Lemmy to support the passkey standard. Now, I assume it will take a while until this is production ready, since the standard seems to be in a quite early stage.

bat and rg I actually have already.... but now you make me waste so much time fiddling with all these ;)