Hacker News Reader

I wouldn't say that reference counting systems are a "software engineering best practice". Mainly because the engineer is not consciously doing anything themselves. It's not like a builder pattern or something. They are just doing what the compiler wants them to do. In fact, there are many ways to get around the compiler errors that feel like an anti-pattern (like using `.clone()` everywhere).

There are other ways to write safe code than just reference counting systems. And arguably, a software engineer would learn more best practices by managing memory more directly.

Kubernetes also has a steep learning curve, and does everything you could dream of, that your docker or managed cloud does not

Do you need them? Will you enjoy using it?

IMO the problem is Rust is very opinionated about how you structure your application, which might not actually match up with what the most logical structure for a particular case is. It depends.

Yeah, i have a distaste for every file is a module approach.

"best practices" however seems a context dependent term.