willrshansen | 6 days ago | on: Making Firefox's right-click not suck with about:config
willrshansen's comments
willrshansen | 1 month ago | on: AI is a horse (2024)
willrshansen | 2 months ago | on: Show HN: I made a spreadsheet where formulas also update backwards
I am a huge fan of the concept though. It's been bugging me for years that my spreadsheet doesn't allow editing text fields after filtering and sorting them down to the subset I want. I have to go all the way back to the mess of unsorted input rows to actually edit them.
willrshansen | 3 months ago | on: The programmers who live in Flatland
willrshansen | 3 months ago | on: 1D Conway's Life glider found, 3.7B cells long
willrshansen | 4 months ago | on: How devtools map minified JS code back to your TypeScript source code
willrshansen | 4 months ago | on: Are-we-fast-yet implementations in Oberon, C++, C, Pascal, Micron and Luon
willrshansen | 5 months ago | on: Is life a form of computation?
willrshansen | 8 months ago | on: Proposal: GUI-first, text-based mechanical CAD inspired by software engineering
Things you've got right:
- Human-readable text file is source of truth
- GUI editing is first-class, because it's easier to work on (most of the time)
Features your proposed solution is missing that I want: - Full power of an established programming language. Yaml or json won't cut it.
- Code and GUI on equal footing. Edit in GUI -> see generated code. Edit in code -> see result on model.
The main problem with Cadquery is that it's entirely code-first, and you lose out on the intuitiveness of GUI editingOne of the less obvious things I really like about dealing with code cad is that feature selection can be based on intent. Like "upper-rightmost feature" rather than "feature closest to this coordinate I just clicked". There's got to be a good way to incorporate this aspect into the "edit in GUI -> code is generated" step (without just requiring manual code editing), but I'm not good enough at UX immediately see it.