bluGill

@ryujin470@fedia.io Most good languages are a variation of ALGOL, Psacal, or LISP. They have added a lot more syntax, but there are only so many ways to represent blocks (both named and unnamed, calling functions, loops and the other basics within the limits of 7 bit ASCII. Even if you expand any language (including symbols you makeup), those still remains the basics and we have learned from painful experience what makes things bad.

@bricked@feddit.org javascript wasn’t written to be like java. Java was the big thing so some marketer found a way to attach java to the name

@ryujin470@fedia.io

I don’t have any 3d printers for fear I would be that guy. Don’t ask about all my other tools. (but I did use my lathe yesterday)

Maybe. I have millions of lines of c++ and making rust work with them will often be more work than just implementing the feature in c++

As a C++ developer Rust’s borrow checker is very interesting - it promises to solve my issues with C++ without the issues that make other languages (ie Java, Python…) have in the real world. (remember we choose C++ for a reason, Java isn’t correct for our application - if Java is correct you should use that instead)

It was implied

I said check out his book, not follow his patterns. There are some great ideas in this build, but also some things Gingery did better - and since Gingery explained why he did a lot of things like he did you will likely in turn be able to adapt the good ideas to this build. The way Gingery does the head stock is much better than this cast in place option for example. Combine the two and you will get better results.

BTW, if you are serious about building a lathe I’d recommend epoxy-granite not concrete or castings. Something more to research before building (or maybe just stop someplace and build - your choice)

Nice, but be sure to check out the Gingery lathe (and the whole series) before building - Gingery did a few things that would improve this if done. (and this does a few things that would improve what Gingery did)