The handholding in rust doesn't come from mut or not. It is from the borrow checker. That is a completely orthogonal language choice to mut by default vs const by default.

I will admit I hate lifetimes and am annoyed that I can't have shared references without making them reference counted. That is where I struggle and time is wasted.

The biggest problem with rust is that while I am trying to make sure I code in a rust approved way, you are off getting things done. Maybe if I had more than a hour to code a week I'd get proficient enough to no longer be slogging through all the time.

The benefit of rust is that once you get it to compile you will absolutely be rewarded with better binaries. Can c give you binaries on par with or better than rust? In theory yes. In practice no. Even the best programmers make the kind of mistakes that rust prevents. Languages like go cannot create binaries on par even in theory. There will always need to be runtime checks for garbage collection.

The question I would pose to you boss is what problem is she trying to solve in switching to rust. If you need better binaries then go for it. If you need faster development then why are you even thinking about it instead of coding?

Reply to this note

Please Login to reply.

Discussion

she's trying to thin out the number of languages we support

nobody else in the company is writing back end server/micrcoservice stuff, only me, and go is the easiest and fastest to get that kind of work done

i also am experienced enough that if we do get lucky and need to scale up to massive infrastructure i have enough clues how to move there when the time comes

here's some irony for you, the Rust devs are only using rust for smart contracts, which are basically dumb shit that can be expressed in BPF, as Solana originally did it, and the number of times that shitcoiners have reinvented the wheel on this is amazing, it was the one thing i found interesting about solana after all was said and done, they didn't invent a fucking new fucking language system, virtual machine

so, this rust, and then Move, which is basically rust cut down and then turned into a structural typed generics language like Go, even down to allowing tuple multiple assignment syntax, and minimising the use of Option, so that is rust, really, and then javascript, because everyone is building web apps

really, they have rust and javascript, and they are saying "for the task that you are the only one doing, and using a language you have 8 yeras experience with, we want to reduce the cost of maintaining devs who can do that"

my junior colleague is a dumbshit who can't say no to his parents or be honest with us about that, but he was able to swim in Go within days

it took him months to get good at working with rust

so if the question is "cost of maintaining staff" then Go is the answer, not fucking rust, not for backend, period, end of fucking story

Yeah not sure about that one. Too many tech stacks is a problem but a worse problem is too few. I have a bad tendency to get very judgemental of developers who want to do everything forever in the first language they ever encountered. "Look ma I hacked together some little JavaScript thing and now I insist that serious backends also be written in js." Or python people sticking with it long after their project has scaled out of making sense in python. "We'll throw hardware at it!"

My all-time most hated language I've been forced to deal with is coldfusion, brought to you by the people who's first "language" was html.

haha, coldfusion... fuck that shit! lol also fuck flash and actionscript as well

ah man that takes me back tho

Luckily I dodged the flash bullet. When I got my first programming job in 2010 and was still full of imposter syndrome trying to pick up the previous devs Ruby projects (also hate) my bosses wanted a second dev and asked my to talk to a candidate they really liked. He had a master's degree in cs and I was just self-taught. Guy only knew flash that was it. Just starting out after college and he had a master's degree in flash development.

I wrote a very long heartfelt email to my bosses saying that I would basically hate working with him and that flash was such a stupid technology that it would probably die in a few years. How wrong I was. Apple killed it a month later by dropping support on iOS and Safari. I often wonder what happened to that poor candidate and if he could get the money back that he paid for his degree.

yeah, i got a scholarship to do a certificate course and the most important thing was asp/vbscript and literally right as we were getting to the last part of that unit microsoft announces dot net

🤦‍♂️

so i learned how to make a basic web 2.0 app with forms and shit and database backend using ODBC and then POOF in a puff of smoke goes my future prospects acruing to my new knowledge

that was probably the act of Microsoft that blackpilled me the most, until i found out what an incredible piece of shit Gates was and learned even more about how microsoft was fucking my life up as i tried to get into tech support and the number of times windows bullshit led me to spending days doing a job that should have been done in 4 hours, and i only charged for 4 hours because it shouldn't have taken that long, but yay microsoft

Yay vbscript! Fun fact. The first production programming thing I did was as an soldering technician when I couldn't find engineering jobs out of college. They had me doing a tedious component testing process that took all week, the majority of time being spent on data entry. I decided to automate it, but they wouldn't let me install a c++ compiler on my workstation. So I proto-typed the whole thing in Excel using vbscript. Saved them three days of labor every time a new batch of sensors came in.

Didn't take long before they bought me a visual studio license, but accidentally got me c# instead of c++. And that, boys and girls, is how I learned c#.

oof delegates

i tried to learn Vala at one point hoping i would one day be able to write desktop apps with gtk3

the complexity of all the things not to do with writing the app kept me from getting anywhere with it and my regular work fixing computers or whatever it was at the time, cleaning classrooms maybe, took up too much time

yeah, for me, my programming career finally started when i tried Go

it was weird at first, and my first year or two with it were pretty bumpy but it was the first language that i was able to encompass a complete, large application, because it lowered the complexity of the parts so much

that's why i use Go, because i can't sit still long enough to decode the umpteen irrelevant shits and procedures that contribute nothing to the solution

that's why i'm so stubborn about it too, you would be if you had never been able to sit still long enough to learn how to IGNORE most of the shit in front of you to get the job done

Go doesn't make you deal with irrelevant shit nearly as much

you have to do that after you make it work, then it has bugs, and then you are really programming