this post was submitted on 15 Jun 2023
90 points (96.9% liked)

Rust Lang

20 readers
1 users here now

Rules [Developing]

Observe our code of conduct

Constructive criticism only

No endless relitigation

No low-effort content

No memes or image macros

No NSFW Content

founded 1 year ago
MODERATORS
 

cross-posted from: https://beehaw.org/post/570507

After the (temporary) defederation announcement of earlier i checked the Lemmy repo to see if there was already a ticket on the federation limiting option like Mastodon’s that people mentioned Lemmy doesn’t yet have. Not only i didn’t find it, i also saw that there’s about 200+ open tickets of variable importance. Also saw that it’s maintained mostly by the two main devs, the difference in commits between them and even the next contributors is vast. This is normal and in other circumstances it’d grow organically, but considering the huge influx of users lately, which will likely take months to slow down, they just don’t have the same time to invest on this, and many things risk being neglected. I’m a sysadmin, haven’t coded anything big in at least a decade and a half beyond small helper scripts in Bash or Python, and haven’t ever touched Rust, so can’t help there, but maybe some of you Rust aficionados can give some time to help essentially all of Lemmy. The same can be said of Kbin of course, although that’s PHP, and there is exacerbated by it being just the single dev.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 16 points 1 year ago (1 children)

Oh yeah, I'm actually a software engineer. I had experience with C and Java, as well as some higher-level languages like Javascript and Python, so for learning Rust it has mainly moreso been learning which function is in which library and how the syntax for the language works, rather than learning programming fundamentals.

[–] [email protected] 0 points 1 year ago* (last edited 1 year ago) (2 children)

Oh my sweet summer child :)

Remember that borrowck is not out to hurt you, it wants to help you, guide you towards enlightenment, and does so with grandfatherly kindness: Making you feel completely stupid.

If you hit a wall make sure to check out the Rust book and work through it, or at least read it: Unless your language background is very specific (let's see C/Pascal or such, plus Haskell, plus very obscure research-grade ML dialects with region-based memory management) Rust semantics are going to kick your ass sooner or later.

[–] [email protected] 8 points 1 year ago (1 children)

Oh my sweet summer child :)

Can we stop with this condescending nonsense?

[–] [email protected] -1 points 1 year ago (1 children)

Can we stop tone-policing friendly heads-up? It's all a long-winded recommendation and reminder to go back to the Rust book if (or rather when) you get stuck.

Even Bryan Cantrill ended up reading through the book, going step by step. There's no shame to it.

[–] [email protected] 5 points 1 year ago (1 children)

I don't find "Oh my sweet summer child :)" all that friendly, I find it condescending and weird. Recommending the Rust book I have no issue with.

[–] [email protected] 2 points 1 year ago

It means as much as "You have not yet experienced the hardships I have, and therefore have an idealistic view of things".

As to weird well yes it's a Game of Thrones reference.

[–] [email protected] 5 points 1 year ago (1 children)

I just started writing more rust code. And until now the borrowck only has been useful. The suggestions inside of the lsp feel like magic. Other lsps only scream at you when you've done something wrong. The rust lsp tells you how to do it right. And sometimes with such a high level of understanding of what I've written, it almost feels like a pair programmer.

[–] [email protected] 3 points 1 year ago

Things definitely got better with non-lexical lifetimes, yes, and that might be the reason that we don't see that many complaints about it, any more.

...but not because it won't at some point be an obstinate bridge troll pointing you in exactly the wrong direction actively hindering you from figuring out what you did wrong (without understanding the underlying semantics), but because people actually had positive interactions with it before, thus not immediately judging it all bad. But it's going to get you, too, just wait for it. It's looming, lurking, in the depths of the compiler, ready to strike when you least suspect :)