How many times have you spent an entire day not moving forward on a project because you couldn’t figure out what the borrow checker was trying to tell you? Maybe you’re just a 10X developer. I feel quite qualified to inform you that for we mere mortals, Rust can very fairly be described as a relatively hard language.
Rust has completely unique paradigms not expressed in any other language! Things that no one coming to Rust has prior experience with. If you cannot admit that makes it harder than some random language that just fucks with syntax, …dude
I’m surprised you put C in there. Its limited vocabulary does mean you don’t have to deal with e.g. C++'s 50 million ways to do something, but this combined with a lack of guardrails makes it agonizingly difficult to do a lot of basic things – most notoriously dealing with strings.
I actually consider C a good beginner language, but only in the sense that 1) it does have that simple toolkit, 2) it and its descendants are widely used, and most importantly 3) the bullshit C makes you deal with gives you a better understanding of what higher-level languages do for you automatically and why. To me, it’s probably the hardest mainstream language to learn after maybe something like x86 or ARM assembly (which, for better or worse, hit points 1 and 3 even harder than C).
I generally agree though that Rust has always been somewhere in the middle for me.
Which paradigm do you even refer to? Lifetimes? A C++ developer who cannot understand lifetimes (at least conceptually) in a day is a terrible developer.
I would know, I work with such people.
To answer your first question, I’ve definitely spent days of my life trying to fix c++ templates because the compiler won’t fucking tell me what’s actually wrong. It loves telling me some unrelated copy constructor is deleted though… And all of that is actually worse with new stuff like ranges. Which are great on paper, but are a maintainability nightmare.
How many times have you spent an entire day not moving forward on a project because you couldn’t figure out what the borrow checker was trying to tell you? Maybe you’re just a 10X developer. I feel quite qualified to inform you that for we mere mortals, Rust can very fairly be described as a relatively hard language.
Rust has completely unique paradigms not expressed in any other language! Things that no one coming to Rust has prior experience with. If you cannot admit that makes it harder than some random language that just fucks with syntax, …dude
deleted by creator
I’m surprised you put C in there. Its limited vocabulary does mean you don’t have to deal with e.g. C++'s 50 million ways to do something, but this combined with a lack of guardrails makes it agonizingly difficult to do a lot of basic things – most notoriously dealing with strings.
I actually consider C a good beginner language, but only in the sense that 1) it does have that simple toolkit, 2) it and its descendants are widely used, and most importantly 3) the bullshit C makes you deal with gives you a better understanding of what higher-level languages do for you automatically and why. To me, it’s probably the hardest mainstream language to learn after maybe something like x86 or ARM assembly (which, for better or worse, hit points 1 and 3 even harder than C).
I generally agree though that Rust has always been somewhere in the middle for me.
Which paradigm do you even refer to? Lifetimes? A C++ developer who cannot understand lifetimes (at least conceptually) in a day is a terrible developer.
I would know, I work with such people.
To answer your first question, I’ve definitely spent days of my life trying to fix c++ templates because the compiler won’t fucking tell me what’s actually wrong. It loves telling me some unrelated copy constructor is deleted though… And all of that is actually worse with new stuff like ranges. Which are great on paper, but are a maintainability nightmare.
I think the borrow checker is trying to tell me to use clone on recursive calls inside a double nested loop!