• 0 Posts
  • 41 Comments
Joined 1 year ago
cake
Cake day: July 14th, 2023

help-circle


  • If a saw sucks ass like the one I used a few days ago, you can’t safely cut through wood and you end up doing dangerous things like putting your body weight on the top of the miter saw to get it down all the way, gripping the piece closer to the blade to try to get it to cut better with less tear out or to not slip, etc…

    There is a big difference between cheaping out on blades/never replacing them and cheaping out on the saw itself. I agree I wouldn’t get the absolute cheapest miter saw, but a relatively cheap one with good blades that are replaced often shouldn’t be significantly more dangerous than a more expensive one.


  • That’s fair, I honestly haven’t used it in a while and forgot the real usage of unsafe code. As I said to another comment, it is a really rough language for game dev as it necessitates very different patterns from other languages. Definitely better to learn game dev itself pretty well first in something like C++, then to learn Rust separately before trying game dev in Rust.



  • The biggest reason is that it’s much harder to write prototype code to test out an idea to see if it’s feasible and feels/looks good enough. I don’t want to be forced to fully plan out my code and deal with borrowing issues before I even have an idea of if this is a good path or not.

    There are options for this with Rust. If you wanted to use pure Rust you could always use unsafe to do prototyping and then come back and refactor if you like it. Alternatively you could write bindings for C/C++ and do prototyping that way.

    Though, I will say that this process gets easier as you gain more experience with Rust memory management.