> How does data-centric work? How is it different from OOP?
Rust doens't have objects. You have structs, which are purely data, and functions, which are purely behavior. OOP puts the two together. So in Rust, you don't tend to design things by saying "what are the objects I need?" but rather "what is the data I am manipulating and how do I manipulate it?"
> Also, what opinion rust devs have over golang?
I am not 100% sure what you're asking here, could you maybe re-phrase? Are you asking why Rust is better than Go?
No, just the opinion in general, why rust over go? I know go is more oriented to distributed systems, but it seems like rust eventually will be used for that as well. And I also see golang being used to build just anything, like gopass for example.
Ah. That's a more interesting question, for sure. :)
I got involved with Rust over Go because if I'm going to use a statically typed language, I need generics. That was the initial thing, but other things ended up going similar ways (I think package management is extremely important, for example.)
I think Go has made great choices to accomplish its goals, but I'm personally more interested in a different set of tradeoffs.
Rust doens't have objects. You have structs, which are purely data, and functions, which are purely behavior. OOP puts the two together. So in Rust, you don't tend to design things by saying "what are the objects I need?" but rather "what is the data I am manipulating and how do I manipulate it?"
> Also, what opinion rust devs have over golang?
I am not 100% sure what you're asking here, could you maybe re-phrase? Are you asking why Rust is better than Go?