You are correct and I am aware of that. However, it also seems that they both refuse to learn it and refuse to work with people at that expert level based on the recent drama, which seems very much like holding things back to me.
Reddit -> Beehaw until I decided I didn’t like older versions of Lemmy (though it seems most things I didn’t like are better now) -> kbin.social (died) -> kbin.run (died) -> fedia.
Japan-based backend software dev.
You are correct and I am aware of that. However, it also seems that they both refuse to learn it and refuse to work with people at that expert level based on the recent drama, which seems very much like holding things back to me.
I mean, I work as a software engineering and if I’m not doing continuing ed, be it about architecture, storage, or new languages, I’m going to be of less value in the marketplace. I’ve learnt languages I didn’t particularly want to in the past for work (though I generally came to tolerate or even like some of them. Not lua, though; lua can go to hell).
If Rust truly is the better, safer option, then these people are holding everything back.
It’s probably going to be a kitten sort of day; I’m stress testing and trying to address the pain points (which so far is mostly on all the other services outside my code that can’t keep up; not a bad place to be).
I would assume so. Grails basically died to SpringBoot (which I thought was sad from years ago as I thought grails did some things better), but I mainly have worked in Go for the last 5 years and a lot of PHP and Java in the 5 before that (then Grails, J2EE, Perl, ASP (pre-dot-net), etc. before all that).
Probably. I think I still have the book in storage back in the US. At some point, I also got “learn c in 24 hours” or something as well.
Something like ruby is a pretty quick way to get up and running with something easy and object-oriented. Groovy if you already have a jvm running (though ruby might be easier depending upon your background)
I learned c from a book from the 80s and then skipped to rust.
The only time I touched c++ was modding games in the early aughts and to try it for a couple coding challenges. I’ve heard templates are a thing of note when it comes to complications but not sure.
As for c# … We don’t talk about that (jk. I had to do it for one or two projects and played with unity a bit ages ago)
I can’t address the first part, but for your last paragraph, if you’re sharing with humans, csv is fine. If you’re sharing with humans and machines, JSON or yaml or something similar is probably fine. If you’re only moving things around to give to machines, what to use depends on constraints you might have and use cases
Opposite here. I got started with Gentoo back in the day of building things from the ground up. Their tutorials all used nano and I just got used to using that. I think when I had casually tried to mess with linux previously, old Mandrake and Redhat in the '90s, I always used the GUI editors, but I also didn’t have a ton of time to mess with it and my hardware wasn’t well-supported.
Ada is named after a human and humans are animals.
I’m not the one asking anything in this case, just findingnothers’ questions and answers
Perl or python for things likely to already be there. Maybe ruby or PHP if you must. I used to work in groovy a lot but I think it requires the JVM
Very TL;DR version: a variable has an owner. If you pass it off to another function, you no longer own it and can’t use it until/unless it gives the variable back. Rust can be really strict on making sure you aren’t trying to use something you don’t own at that time. The documentation explains it better than this (and I wrote a longer post but accidentally closed the window and lost it). See also mutability and lifetimes for some pain points people might not be used to.
I agree with the others who say to start with The Book – https://doc.rust-lang.org/book/
From there, start trying to create small things that you might want or need to do (parsing JSON is something that I needed to do and I started there).
From there, you will learn to fight the borrow checker and start to feel how rust is working. This will be annoying at first, but get better over time (at least in older versions of Rust; I haven’t used it in a while so it may be different now).
Yeah, it sucks. In the cases where it was really helpful, I couldn’t upvote the answer that helped me solve my issue (usually with some more poorly-documented library or something).
Never. IIRC, I also couldn’t upvote good solutions because I had never posted or something, though I may be mis-remembering.
They’ve been awful for many, many years at this point. I’ve no idea why people keep giving them money and expecting them to not be awful.