I have to respectfully disagree to a small extent.
-
Absolutely it's difficult in the beginning of learning a new language to rewrite from one language to another. But, correlation and failure provide some of the best learning. It depends on if you're up to the challenge. Also, be rewriting from a common language to a newer language helps promote the new one.
-
Totally agree...Rust is not really OOP because of interface inheritance or composition. But, I as I delved more into the subject of inheritance, I realized, I already write my Java using interface inheritance up to the point I refuse others' code like JavaFX.
-
Check out OrbTk. It's written using ECS concepts. They took the idea from the gaming industry and said "hey it works here, what about in Rust's way of doing things?" From what I've seen, it totally falls in line with Rust's composition and interface inheritance. But, that's where I get stuck....the full understanding of entities, components, states...I think I have a crude basic understanding. I watched a video on YouTube on the data-oriented implementation of a gui by using ECS concepts and why it was chosen Data Oriented GUI in Rust by Raph Levien - Bay Area Rust Meetup - YouTube but I could only grasp portions of it. I attribute that to being out of touch with programming for such a long time and coming back to it....think BASIC, Pascal, MSDOS 3.3, etc.