This is so wrong. I would absolutely prefer no comments over incorrect comments, which is exactly what happens when things get over commented

Exactly this. Anyhow makes error handling in rust actually a joy. It’s only something you need to consider if you’re writing a library for others to use, and in that case, it’s good that rust forces you to be very very explicit

That syntax looks atrocious

Are you using an IDE like rustrover? Rust is by far the easiest language I’ve worked with. It makes it so the only way to write code is the right way

Terrible meme. Go is bad and you should feel bad

Yes. They’re unsurprisingly called scalies

Yeah, you fit right in

Look at some of their other comments. They’ll fit right in with the other lemmy devs

Wtf

Rust just has lousy compiler warnings.

You’re the only person I’ve ever heard this from. Rust’s compiler warnings are amazing. Like 2nd to none

You’re missing the point. Tools are different. Trying to learn and use rust by writing unsafe bubble sort is pointless. Use it to actually accomplish something and you’ll find out just how amazing it is.

Using the ecosystem that exists to be productive and not have to think at all about whether what you’re doing is correct is the point. It catches the subtle errors for you and lets you use the powerful libraries like clap for command line parsing, tokio, etc.

Once you get the hang of rust you don’t ever need to ask it to do unsafe things. It’s not really any faster to do things unsafe

I think knowing about frontend is important for a senior or higher level engineer. I would expect someone at that level to be able to contribute where necessary, and know enough to make sane decisions and know when those decisions impact backend/frontend. But to be equally good at both isn’t reasonable

At least it’s not needed at runtime. The node modules are, right?

There’s nothing keeping the comments up to date with the code. Comments should be sparse and only on sections that aren’t obvious why they’re being done

No, because that’s not valid json

How about only a laptop monitor?

For servers I don’t want rolling releases

Yeah I wasn’t talking about servers.

I don’t get it. You end up with ancient packages and have to install ppas to get modern tools, or write code that can’t take advantage of modern tools and have to do workarounds

I don’t know how you deal with non rolling releases on your machines you actually use for work. By the end of the lifecycle all the tools are ancient