snaggen

joined 2 years ago
 

@nnethercote@mas.to wrote:

I have rewritten the Build Configuration chapter of the Rust Performance Book.

https://nnethercote.github.io/perf-book/build-configuration.html

It's now a much better guide to all the ways you can change the performance characteristics of your Rust program without changing its source code. These characteristics include runtime speed, memory use, binary size, and compile times.

Big improvements to your Rust program's performance are possible with simple changes. Try these things out!

[–] snaggen@programming.dev 11 points 2 years ago (1 children)

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.

[–] snaggen@programming.dev 17 points 2 years ago* (last edited 2 years ago) (2 children)

Absolutely nothing.... but for some reason I find it interesting when people rewrite things that I didn't know needed rewrites. Sometimes these projects are doing someting really interesting. Grep is one such example, noone was saying that grep needed a replacement. In fact, it was used as a benchmark for regex (which is how rg started, to compare rust regex against grep), then someone creates rg that outperforms grep and is much nicer to use. That is also why I keep an eye on GitOxide, since nobody ever accused git of being slow, yet there are someone rewriting git with amazing performance improvements.

[–] snaggen@programming.dev 2 points 2 years ago (2 children)

I still think this works better with a rust hashtag, than as a community ping, since that creates a new post in the Lemmy forum.

[–] snaggen@programming.dev 3 points 2 years ago (4 children)

Ok, this is from Mastodon.... Then I'm sorry if I sounded a bit hars, then I understand the format of this post.

[–] snaggen@programming.dev 4 points 2 years ago (14 children)

This seems to be nothing other than shameless self promotion. Mods?

[–] snaggen@programming.dev 6 points 2 years ago

In short, running an instance requires quite a bit of work, so having a really small instance might be quiet a challenge. Programming.dev is still niche, but large enough to not be a one man show.

[–] snaggen@programming.dev 18 points 2 years ago* (last edited 2 years ago) (1 children)

The problem with lemmyrs.org seems to be that it is poorly maintained, still on Lemmy 17.4 and few moderators aso. Programming.dev otoh is very well maintained, well moderated and still not a huge centralized place. It also host many other interesting resources for programmers. Also, the structure of lemmyrs.org with many smaller communities doesn't work really well at the moment, it would require a huge number of users to avoid these communities being ghost towns.

[–] snaggen@programming.dev 3 points 2 years ago

Well, duplicate communities might also be on purpose, to lessen centralization. I see many that try to migrate away from lemmy.ml, and this community is one of them. I agree that it might be a bit confusing, but it is easily worked around by subscribing to both communities.

[–] snaggen@programming.dev 5 points 2 years ago* (last edited 2 years ago) (2 children)

How is communities undiscoverable? There are services for this https://lemmyverse.net/communities , of course it would be nice to have that more integrated in to Lemmy, but it is still there.

view more: ‹ prev next ›