|
I have read that it can be a real pain (not that I have coded in Rust) to manage memory because it has memory ownership. That's purely anecdotal by the by.
|
|
|
|
|
Visual Code has an extension; Rust Extension Pack by Swellaby
I've been trying to learn it also but, like you I just haven't been able to wrap my head around it. (I am old...that's my excuse and I'm sticking to it)
The most expensive tool is a cheap tool. Gareth Branwyn
JaxCoder.com
|
|
|
|
|
Thanks! I'll check that out.
To err is human. Fortune favors the monsters.
|
|
|
|
|
From what I have seen it is a mixture of C, Java, Javscript, Python, C++ etc. The main difficulty is the designers' use of obscure terminology rather than using the same words that most developers are used to. I can see no reason why I would ever need it.
I always found that trying to learn a new language after lunch put me to sleep.
|
|
|
|
|
maybe you are a little rusty ?
(sorry, I'll get my coat)
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
It looks like text speak: no caps, pointless abbreviations, and words that don't mean what they mean in conventional terms. Might be ideal for programming with your thumbs only.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Gerry Schmitz wrote: ...looks like text speak: no caps, pointless abbreviations, and words that don't mean what they mean in conventional terms. Sounds like *nix.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
TNCaver wrote: Sounds like *nix ... or cmd or powershell or ...
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Part of it probably is because you're older, but not because of any mental breakdown or slowdown but because what you've learned and worked with so far has burned their paradigms into your brain, and your brain is resisting Rust's paradigm.
Or I could just be blowing hot air; I've not looked closely enough at Rust syntax to know how different it is.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
I don't think it's age related. Apart from some exceptional cases brain can be trained similarly to muscles regardless of how old we are. It rather can be something connected to some sort of fatigue or lack of motivation or combination of both factors even though that you can think that you're motivated in reality it can be not true.
|
|
|
|
|
Our brains get full. Would be nice to have selective memory erasure to free up some of it for other uses.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
|
that's too obvious.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Not enough anti-oxidants?
|
|
|
|
|
It's not your age, and it's not you in any other way. It's Rust. I read through some of the documentation once and didn't care for it. I decided to give it a second chance. That was enough to convince me that it was bizarre and that I wasn't interested. Another language whose designers either think they're your parents or have PTSD from bad pointer experiences.
|
|
|
|
|
why do you need to pick RUST?
diligent hands rule....
|
|
|
|
|
None of this is about need. And I'm pretty sure Rust isn't an acronym?
To err is human. Fortune favors the monsters.
|
|
|
|
|
Seems to me like you're likely already rather intimate with hardware and how things work in computers.
From a quick look at the code-samples, it felt like stepping back into about 1993 and Turbo Pascal.
Pointers are trivial. Memory safety and leaks aren't exactly the hardest things to keep track of either.
Certainly not the view held universally, but reasonably common all the same.
It feels like the language introduces unnecessary complexity in pursuit of the mission to dumb-it-down.
EXACTLY the same mistake so many HTML/JS frameworks force upon their users.
println!("Nah thanks. Keep yer oxidised rubbish Mozilla");
Oh... and here's yer bang back too ( ! )
FFS - it's an exclamation mark ya willies.
Rant aside - thanks for the impetus to finally have a look at it. That was 20 minutes of my life I'll sadly never get back.
|
|
|
|
|
I'm glad I'm not the only one that feels that way!
To err is human. Fortune favors the monsters.
|
|
|
|
|
honey the codewitch wrote: I read somewhere that our intelligence and mental flexibility peaks in our late 20s?
Arthur C. Clarke's First Law:: When a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is very probably wrong.
Clarke went on to define "elderly": In Mathematics and the physical sciences, anyone over 30. In biology, senile decay is at times postponed to the 40s.
Join the club...
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
I thought witches used a lot of greasy chicken in their rituals. It's hard to rust when when greasy. Start using lean chicken, but your casting skill will suffer for it.
|
|
|
|
|
Too many letters in the name?
Surely, the shorter the name, the better the language.
|
|
|
|
|
I've been considering learning Rust for the challenge of it, but you know, there are plenty of challenges to choose from, so maybe I'll skip this one. It would only be an ego-boost for me personally, and from the sound of this 'review', perhaps not
|
|
|
|
|
For me, I learn new languages by reading as much source code as I can.
This allows my brain to pickup the constructs/flows pretty quickly.
This works really well... UNTIL you get to heavily "decorated" languages.
.NET web code shocked my system.
Then some of it is about the language helping to change programming detail location.
I have some old code in my favorite language, where I was practicing some of this. It's
really cool. Everything is based on a base class that knows how to "process" something.
Then I inherited from that with 2-3 implementations based on filetypes, expectations.
One master controller loop that dealt with setting orders.
Every process was nice and tight/small. To this day, it's the hardest code for me to modify.
I have re-immerse myself in the code.
Unfortunately, I don't know RUST but my initial take is that the language contains a paradigm shift.
Either in Decorations for some level of control, or conceptually to organize the code. (If that makes sense).
Once you wrap your arms around it (like the transition to C++, which was BRUTAL because of all of these Object Rules),
things will likely fall in place.
But I still think it's easiest to start by reading someone elses code. And modify it! Get dirty.
Also, one other commenter mentioned getting older (or more mature), your definition of "knowing" something changes, and gets a lot of depth. When we were kids, writing 2 C++ programs meant we KNEW C++ (ROTFLMAO). Most people came from C, and could write C code in C++... A huge difference, and we "know" that at a deeper level now!
|
|
|
|
|
Kirk 10389821 wrote: Also, one other commenter mentioned getting older (or more mature), your definition of "knowing" something changes, and gets a lot of depth. When we were kids, writing 2 C++ programs meant we KNEW C++ (ROTFLMAO). Most people came from C, and could write C code in C++... A huge difference, and we "know" that at a deeper level now!
I think my problem might be a bit of imposter syndrome. Even now I don't think I can code very well in C++, if I'm being honest with myself. I fake my confidence, because I figure maybe I can fake it til I make it.
That said, intellectually I know I underestimate myself when I assess my abilities.
And most of my C++ code could not be written in C very readily. I use a lot of "advanced" C++ features like metaprogramming.
To err is human. Fortune favors the monsters.
modified 11-Jul-22 10:32am.
|
|
|
|