ROrowanG077·Oct 18, 2021
Doesn't https://github.com/CadQuery/CQ-editor work on MacOS? I don't really see how development has fizzed out. There have been quite a few commits the last couple of months.
In Code CAD – Use code to create CAD modelsCadQuery
CQ-editor
Python2020–2026
CadQuery / CQ-editor
CQ-editor
CadQuery GUI editor based on PyQT
9Distinct people
10Mentions
1Explicit recommenders
1.3KGitHub stars
What to know before exploring
What it is
CadQuery GUI editor based on PyQT
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
If you look at this and you think "wow, I love the idea of CAD-as-code but I wish it was a more sane language" then have a look at CadQuery:…
wren6991 used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- cadquery/cadquery · linked in 3 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 9:02:44 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year10 dated mentions
Observed mentions: 2020-08-23 13:28:55 UTC to 2026-10-10 21:23:50 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
2 sources> I'm curious, what makes you so opposed to it
I confess to having not kept a very detailed track of the headaches conda has caused me over the years, but here are my recollections:
- conda plain and simple failing to install with a cryptic error message after downloading multiple gigabytes of crap only to test a small piece of software. Back then (slow download / disk writes / CPUs), easily an hour wasted.
- conda ruining my existing pip install and silently overwriting apt-get managed packages.
- conda unilaterally grafting bash code in my .bashrc, a practice I find - to remain polite - distasteful, not to mention the (IIRC) creation of a giant turd of a repo in my home directory.
- conda, when used to run tensorflow based packages on my NVidia linux box completely wrecking the existing NVidia drivers installs to the
Read the rest
point of it booting in "safe mode" or giving me a black screen.
- post conda install, some binaries didn't want to run anymore because conda-installed libs were newer.
To be fair these grievances are old: I've avoided conda like the plague for - easily - the last 5 years, and they might have cleaned up their act.
However, I still find the notion of having to install 2 gigs worth of stuff on my machine only to try a simple CAD package for a few hours a rather offending proposition. Call me an old curmudgeon if you have to.
To be fair to the cadquery folks: they seem to have realized the issue and they now offer what looks like a somewhat self contained binary dowload of the cq-editor package [2].
Finally, I'll leave you with this, taken from the cadquery homepage itself [1] (note the use of the word "polluting" in there, looks like I'm not the only one feeling this way):
For those unfamiliar (or uncomfortable) with Anaconda, it is probably best to install Miniconda to a local directory and to avoid running conda init. After performing a local directory installation, Miniconda can be activated via the [scripts,bin]/activate scripts. This will help avoid polluting and breaking the local Python installation. In Linux, the local directory installation method looks something like this
[1] https://github.com/CadQuery/cadquery#alternative-anaconda-in...
[2] https://github.com/CadQuery/CQ-editor/releases