public
/
til.jpace121
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Compare commits

base: public:eb2e1b685258458ea9e50961ff437993c264fddd
Branches Tags
public:main
..
compare: public:e40bea2aaab02cd12b8d0d80c3ae2fba01130702
Branches Tags
public:main

No commits in common. "eb2e1b685258458ea9e50961ff437993c264fddd" and "e40bea2aaab02cd12b8d0d80c3ae2fba01130702" have entirely different histories.
eb2e1b6852 ... e40bea2aaa

2 changed files with 7 additions and 6 deletions
Show Stats Expand all files Collapse all files

11
posts/cadquery-direct-api.qmd
View File

@ -43,18 +43,19 @@ will:
This may seem confusing, but if you've worked with Fusion360 or Creo, you've basically done
the same thing (see the timeline in the bottom of the window in Fusion360 or the history in Creo).
I've found that once the idea clicks what's going on isn't that hard to work out.
I've found that it once the idea clicks what's going on isn't that hard to work out.
What is a pain to work out is when something goes wrong.
It is very hard to introspect what's happening at each step.
Particularly when so much is written on basically one line, which isn't a requirment per se,
Its very hard to introspect what's happening at each step.
Particularly when so much is wirtten on basically one line, which isn't a requirment per se,
but definitely the suggested workflow.
Regardless, the actions in each of the lines is extremely dependent on state hidden in the workplane
that is basically impossible to tease out.
It is also really hard to organize things in a way that allows for code reuse.
What I've found more challenging is it is really hard to organize things in a way that allows for code
reuse.
Specifically, I've worked on two projects where I've wanted to reuse sketches in multiple places,
and in neither case could I really find a nice way to do that while using the Fluent API.
and in neither case could I really find a nice way to do that while using the Fluid API.
I've found the Direct API to make this much easier.
The Direct API is much closer to "normal" OOP programming, where objects are made by calling

2
posts/powf_is_slow.md
View File

@ -42,7 +42,7 @@ of `libm::powf`.
When compiling with the default optimization level (`-O3`), I saw a similar performance
increase, but not when I switched to compiling with `--release`, which I found interesting,
and which underscores the importance of building in `--release` when shipping Rust binaries.
and which underscores the importance of building in `--release` which shipping Rust binaries.
[libm]: https://github.com/rust-lang/libm
[micromath]: https://github.com/tarcieri/micromath