I mean, I am all in for labeling, but banning it? Is that what’s happening? why would anyone do that

it’s somehow scary how many overlaps there are with falling empires from the past, I miss the USA that used to be

I learned a bit of rust and I think it’s just about getting used to it. It’s fairly subjective, and people say the same about C++. I also prefer the C syntax because I find it’s simplicity extremely elegant and prefer it to have fewer features. And I like it for it’s consistency, on linux the FHS is based up on C, and it just somewhat feels ugly to break that consistency.

But I also acknowledge the advantages of rust.

Yeah, it’s a weird combo for FOSS because macOS is quite the opposite of what FOSS stands for. However, quite a few people think it’s the best and… I don’t know

it works just fine because people generally earn the same depending on education, experience and profession. There are tools online to check what range you can expect based on your parameters, and then there is some flexibility based on your person/skills. The salary is then negotiated during the application phase.

Yeah, I don’t think there’s anything wrong with coding in rust for people who like it. But I do think it’s quite a bit of useless work that could be spent more wisely on new products instead of rewriting things that we already have

It is possible, it would bring in quite a few restrictions though. The bigger problem I see is that it wouldn’t be entirely clear as an end user whether a program is memory safe or not. However, this isn’t the case with rust neither. Maybe some kind of certification would help

not a big fan of rust personally. I think it would be much smarter to bring borrow checking to C through annotations. That way we would not have to rewrite the whole world