dschroer

I have been using their API/MCP tooling. If I remember correctly its still experimental but it does work. I have it hooked up to my OpenWebUI instance.

https://github.com/kagisearch/kagimcp https://kagi.com/api/docs/openapi https://kagi.com/api/docs/openapi/section/mcp

I did. It's behind me now and more importantly I'm fully recovered mentally and physically.

I don't live in the states so it's not as dramatic legally as you may imagine.

You still need to be careful. I'm an avid climber. Most autobelay accidents happen because people don't clip in properly. However for me the auto belay cable broke after catching me. Resulted in five minor spinal fractures.

So from my experience I would say at least Google what are the common auto belay manufacturers and only use gyms that have them. True Blue and Perfect Decent are the only auto belays I will touch now.

TBH I am not sure but I suspect the answer is yes. I use OpenCascade as the base CAD kernel and it handles things like Z-fighting a lot better. I built DSLCAD after completing porting OpenSCAD to wasm because I wanted a better programmatic CAD platform. It's development is really "as I need it" from then on.

For those who are interested. I have been working on a similar CAD Modeler. I think of it as a spiritual successor to OpenSCAD.

It has support for bidirectional modeling (ex: get the height and width of an object and use it later) and multi part workflows to design more complex works.

https://www.dslcad.com/

My partner is a medical doctor. She can't navigate around. I don't think there is any link. Navigation was something that I was taught early and is a skill like anything else.

There is something nice and pure about this site. It is probably just coincidence and random that the number 37 is seen around. Likely something along the lines of the Baader-Meinhof phenomenon.

However none of that matters. What matters is the site is there for all of us to enjoy. It made me smile and I appreciate that.

Good write-up. What was understated but I appreciate was that this optimization was done late and after being picked up via profiling. For devs there is sometimes a drive to do this kind of work early. It really should always be done late just as in this post.

You have a super interesting use case. Can you reach out on the github issues so that we can track it? From what I can tell you are trying to generate GCode directly from the software is that the case?

The goal of pipe is to allow the code to read top to bottom. I always found it hard to explain the way an OpenSCAD program reads upwards when nesting operations.

As for the syntax there are certainly a lot of ways it could feel. JS devs would likely be familiar with =>, F# and Ocaml |>, Java ->. In the end I just picked one that felt natural to type for myself. From my experience if you write in enough languages you develop the ability to switch as needed.

For sure I would accept a PR! One of the goals I have here is to try and make it approachable to expand for others. If you have an idea on how to make this work please feel free to work on it.

To save time up front I would suggest doing a bit of design work. Feel free to make an issue and post things like example code snippets of how you would like to see this work. We can work together to make this feature a reality.

You are probably right. The Linux hacker in me still kind of prefers having a bit of style to names. Maybe over time this will change.

Thanks for checking it out. I am glad you like it.

1. Now that you have asked for it, I certainly plan on adding `loft`. Thank you for the suggestion. Looking quickly it looks quite reasonable to implement. I would expect to add it in the near future.

2. It is a digital art coloring book image that I filled in and used as a background.

Hey. I'm glad that this is what you are looking for. At the moment there isn't constraint based modeling. However given that you have a programming language at your disposal you can model your constraints yourself.

I am not very familiar with the homebrew packaging process. I would be happy if someone wants to help set that up.

Ill take a look into KittyCAD. Seems like a cool idea and is worth digging further into.

From my understanding JSCAD is aiming to be 1:1 compatible with OpenSCAD. So both strengths and limitations will come with that.

DSLCAD is a new take on the idea. Right now it doesn't support bending, however from my personal opinion, DSLCAD is simpler to develop for and should make it an easier platform to add bending support to.

Feel free to add an issue asking for bending and we can hash out how to make it work. Getting the API down is often as hard or harder then implementing the solution.

Having renders "auto focus" has been on my mind. Probably will be coming soon. I was focused on getting the language and runtime in better shape first.

Fixed. Thank you :)

Its using open cascade.

I am not a mechanical engineer. I am a software developer however I have worked closely with engineers and have some experience with CAD applications.

Really most of my decisions come from working on larger projects in OpenSCAD as well as my contributions to the OpenSCAD project (WASM port).

Interesting. I just tried your example and it worked on my end.

Have you tried rendering any of the examples in the repo? I know its not ideal but just to see what is going on. Please add an issue on the repo so I can try to fix the issue you are experiencing.

Not yet. Its certainly something that I want to support. I want to avoid supporting all the formats so settling on a few clear options in the space is the goal. Right now its only STL since its super standard and doesn't force me to cover everything. I will likely move away from STL as things settle.

Feel free to add a ticket requesting your favorite and I can look into moving to that format in the future.

Should be fixed now. CI issue

It is designed for use with an external editor. It watches the files and hot reloads when you save changes. I didn't want to do a sub par job building my own text editor.

I cant wait to hear about how it turns out for you.

Thanks for the suggestion. Ill see what I can add to make it clear.

Very cool project. I love the fact that you did it in a weekend.

I have had this feeling a lot with my project. One thing that might work is break down the compiler itself into smaller projects. If you cant solve it all in a weekend try solving just a part of it and then calling that the project. Then move on to the next part. In the end up are building up to it without overwhelming yourself.