Comment on Hi, I want to start programming but dunno where to start and which language to learn
KindaABigDyl@programming.dev 1 year ago
Pick Rust, learn Bevy, and make a Flappy Bird clone.
Comment on Hi, I want to start programming but dunno where to start and which language to learn
KindaABigDyl@programming.dev 1 year ago
Pick Rust, learn Bevy, and make a Flappy Bird clone.
lysdexic@programming.dev 1 year ago
Rust is renowned for being hard and frustrating to onboard onto. I don’t think this is a wise suggestion.
users.rust-lang.org/t/…/2
KindaABigDyl@programming.dev 1 year ago
You missed the point
lysdexic@programming.dev 1 year ago
What point do you think I missed?
KindaABigDyl@programming.dev 1 year ago
What I said:
We could go on for hours debating what the best beginner language, environment, project, etc is, but the important thing is that they pick something and do it.
I gave them a specific thing to get started on. That’s the important thing.
Like I said:
That’s why I said you missed the point. I don’t think you read my reply at all and just stopped at the first word lol
mmstick@lemmy.world 1 year ago
This is very over-exaggerated. A lot of people started with C or C++ as their first language. Both of which are significantly harder than learning Rust. In fact, I had a much easier time learning Rust than I had with Python and Java because the Rust compiler’s always had great error messages and documentation. Which then significantly boosted my ability to write C and C++. If, in an alternate reality, I had started learning programming today, I would recommend to my alternate self to start with Rust. Especially now that it’s gotten so much easier than when I had learned Rust when it was still in alpha. Error messages have gotten very detailed lately, to the point where many of them show the precise code to write to fix the error. The compiler’s also much less strict with borrowing and lifetimes.
lysdexic@programming.dev 1 year ago
That took place over two decades ago. There were no better alternatives back then. Times have changed.
This is simply not true. It’s far simpler and less frustrating to work on either C or C++ for the simple reason that you can shoot yourself in the foot anywhere you’d like. In Rust, newbies have to alternative to endure the compiler enforcing its safety constraints anywhere they’d like. Rust is also a far more complex and extensive language that enforces memory safety rules that can and very often are very frustrating to handle by those who don’t have a firm grasp on them.
MajorHavoc@lemmy.world 1 year ago
Agreed. I lound learning C decades ago was a pain in the ass. And I found learning Rust last year was a huge pain in the ass.
mmstick@lemmy.world 1 year ago
You’re not making the strong case that you think you are. Quite the opposite. The ease of “shooting yourself in the foot” is precisely what makes it so difficult to learn. Segmentation faults and random memory corruption make it incredibly hard to get started with programming. So much so that many people give up when it gets too difficult to diagnose them. The compiler typically providing no help at all for diagnosing where the memory handling flaws are.
Rust’s constraints are very clear and concise in comparison, with a helpful compiler that will teach you how to handle memory correctly. I believe you’re mistakenly assuming it’s more difficult to work with than it really is. For example, imagine telling someone that pattern matching in Rust is more difficult than constructing unions and casting pointers in C. I’ve worked with a number of people over the years that had little experience in programming outside Rust.
onlinepersona@programming.dev 1 year ago
tourofrust.com