Just kidding. But would you mind sharing what you find so compelling about CadQuery?
As a mechanical person, these code to CAD tools make as much sense to me as suggesting you should write programs with a compass and straight edge.
Just kidding. But would you mind sharing what you find so compelling about CadQuery?
As a mechanical person, these code to CAD tools make as much sense to me as suggesting you should write programs with a compass and straight edge.
I don't know enough about the underlying proof-of-work stuff to comment on how effective this could be, but I think it's pretty funny that the UI examples say "I'm a human".
I guess "there's only a few of me at most" or "I could allocate enough computation to this that I'm probably not up to no good" don't read as clearly.
I've consulted for similar size businesses, and shipping integration was always the reason to not support international shipments. Send them an email, you'll almost certainly hear back from a real person and if you let them know what you want to order they can probably make it happen.
This is probably just my opinion, but I kept thinking that a better word for "drive" given the domain would be "clock". It's basically a binary clock signal driving these, right? Maybe "clock drive"?
> The added constant seems artificial, but it's just viewing the results from the point of view of a client with 30ms ping time. Otherwise the log scaled x-axis would overemphasize the importance of a few milliseconds at the low end.
I thought this was interesting - maybe it's a standard practice I was just unaware of but it seems like a smart trick.
They are pretty great at converting data between formats, but I always worry there's a small chance it changes the actual data in the output in some small but misleading way.