snaggen

Also, this community is coming along nicely. We are in the top tree communities on programming.dev if you look at the list of communities. We are the highest ranked programming language community, ahead of Python. So, I don't see any need for artificially inflating this community.

Edit: Link to the community page https://programming.dev/communities

No, just look at the rust community on Lemmy that imports stuff like this. It is flooded with a lot of content, but that makes it impossible to follow and interact with. Also, if you know it is a bot that posted, you don't have any reason to interact with that post. Automatic imports tend to feel like spam, so please don't do this....

I'd rather see that people keep an eye open for suitable news, or ask genuine questions and write other interesting posts by hand. It may be a bit slow early on like it is now, but that is somewhat in proportion to the engagement so it all fits together.

When you compare "idea to deployment" speed, a dynamic language will always win. However, much of this win is due to a dynamic language will let you deploy with a lot of bugs. So, you will then have to spend lot of time fixing production issues. Rust will force you to fix most of these issues before you can deploy, hence it feels slower in this aspect. I previously worked for 10 years with a huge perl code base, and I trade the deployment speed for stability in production any time.

If you refer to bindgen it also supports C++, and since Mozilla who was the main driver of rust uses C++ I assume the bindgen for that is pretty good.

Yes, but all programmers have a love/hate relationship to their languages and toolchains. When I started off back in the 90:s, my prefereed language was Perl, it was amazing, but it was also a nightmare in some aspects... and unfortunately the larger the project the larger the nightmares. I assume Python is probably pretty much the same, even though I have avoided to work with dynamic languages in very large scale projects due to the support nightmares that comes with them. So I assume the Rust cult, is based on the fact that the rust frustration comes a lot from the strictness of the language, but that becomes less of a problem the more you use it (since your skills improve) and at that point the strictness instead gives the reward of reliability and efficiency.

So, while dynamic languages may frustrate you the more you use it (since the projects grows and it is a nightmare to maintain), rust will instead reward you over time.

Always nice to get a summary of the week. I had not seen about the websocket implementation, nice to see that Rust is yet again pushing the limits for performance.

If that works for you and you are happy with it, fine. But sudo-rs seems to have a bit of a different usecase since it is intended as a drop in replacement for sudo, hence it must be able to handle the sudoers file aso. It still removes some of the never-used obscure functionality that sudo had, so it is probably a lot smaller code base than original sudo.

That varies quite a lot... but in general, the small tools seems to start as someone adding color and bling, possibly some nice things like automatic pager (like in bat). Still often nice additions though. For larger stuff like rg and gitoxide the authors seems to have done quite a lot of research and are really experts in their field. You don't improve grep and git by accident.

I like that they now have rustls 0.21 support! Not that I know anything wrong with rustls 0.20, but I was always annoyed that cargo outdated pointed out that my rustls was outdated, and I wan't allowed to fix it :)

https://programming.dev/comment/2399461

A bit about passkeys https://www.yubico.com/blog/a-yubico-faq-about-passkeys/