I&#x27;d definitely have an easier time overall with C#, no questions asked. I actually tried it briefly, but after a week of not being able to get a development environment communicating with Solidworks, I decided it was unjustified for making an MVP.<p>It&#x27;s actually been a whole lot longer than 7 months since I worked on it. The whole thing was basically one monolithic commit I did after writing the snapshotting utility while doing release documentation for a product I was managing. Since then (and even while I was working on it) I&#x27;ve thought of a lot of much better approaches to this than I was taking with the macro. The macro was just a very early proof of concept. I&#x27;m also not totally sold on the yaml choice, I can see a lot of reasons to go with an open binary format -- but I think part of the success of JSON has been predicated on its choice of universally-parseable text. The ultimate goal would be to create a new CAD program marketed towards the sub-$100 software market. I&#x27;d couple that with a version control system specifically tailored (even if just in UI) to a hardware workflow, and then get recurring revenue from a github-like service. Really neat project and I&#x27;m confident I could execute on it successfully.<p>Except I&#x27;ve actually put this project on hold while I work on something more important to me - creating, implementing, and financially sustaining an open, encrypted, distributable social networking protocol (<a href="https:&#x2F;&#x2F;www.ethyr.net&#x2F;blog&#x2F;muse-101.html" rel="nofollow">https:&#x2F;&#x2F;www.ethyr.net&#x2F;blog&#x2F;muse-101.html</a>). Fixing solid modeling is an awesome and potentially very lucrative endeavor, but it&#x27;s much less timing sensitive (and much less personally meaningful) than my current project is.