96
Lemmy is in serious need of more devs [CROSS POST]
(self.rustlang)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Jun 2023
96 points (98.0% liked)
Rust Lang
58 readers
1 users here now
Rules [Developing]
Observe our code of conduct
- Strive to treat others with respect, patience, kindness, and empathy.
- We observe the Rust Project Code of Conduct.
- Submissions must be on-topic
- Posts must reference Rust or relate to things using Rust. For content that does not, use a text post to explain its relevance.
- Post titles should include useful context.
- For Rust questions, use the stickied Q&A thread. [TBD]
- Arts-and-crafts posts are permitted on weekends.
- No meta posts; message the mods instead.
Constructive criticism only
- Criticism is encouraged, though it must be constructive, useful and actionable.
- If criticizing a project on GitHub, you may not link directly to the project’s issue tracker. Please create a read-only mirror and link that instead.
- Keep things in perspective
- A programming language is rarely worth getting worked up over.
- No zealotry or fanaticism.
- Be charitable in intent. Err on the side of giving others the benefit of the doubt.
No endless relitigation
- Avoid re-treading topics that have been long-settled or utterly exhausted.
- Avoid bikeshedding.
- This is not an official Rust forum, and cannot fulfill feature requests. Use the official venues for that.
No low-effort content
- Showing off your new projects is fine
No memes or image macros
- Please find other communities to post memes
No NSFW Content
- There are many other NSFW communities, let’s keep this related to the language
founded 2 years ago
MODERATORS
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.
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.
Can we stop with this condescending nonsense?
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.
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.
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.
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.
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 :)