willrshansen

Joined 1 year ago

Karma

39

Submissions

30

Member since

Jul 9

View on Hacker News

Recent submissions

Comment · 24 days ago

Given how little they've changed over the years, sharks are very successful.

Comment · 1 month ago

Was expecting time travelling moon robots. :(

Comment · 2 months ago

Of course. They are slowing down intentionally because their technology is too powerful. They could totally go faster if they wanted to. No bamboozle.

Comment · 4 months ago

First image I see should be a difference of how the merges work.

Comment · 4 months ago

also r/datahoarder

Comment · 6 months ago

Big fan overall. Designed a tension sensitive winch with this a few years back.

Doing CAD with code seems like obviously the right move to me. The ability to just write new functions in python and do version control with git are super powerful.

The big thing that struck me as innovative with CadQuery is the design intent query part. Selecting model geometry by relation to other geometry is way more resilient to changes ealier in the model's history than the regular "that point right there" you get with just clicking a point.

That the developers acknowledge that seeing the model at various steps in the script is important, and so have the CQ-editor, is also a point in their favour.

I do have a gripe though:

Having to keep all the geometry selection stuff relating to the model in my head is hard. I want gui tools that write code.

Like if I have a complex model, and variables assigned to various parts of the geometry. I want to be able to see that geometry highlighted and labeled, so I know what's easily selectable, and I want to be able to click buttons based on my design intent and get immediate visual feedback, and have each of those button presses added as code as I do them.

Look at this example model: https://cadquery.readthedocs.io/en/latest/examples.html#a-pa...

This bit that selects some points?

  # compute centers for screw holes
  topOfLidCenters = (
    cutlip
    .faces(">Z")
    .workplane(centerOption="CenterOfMass")
    .rect(POSTWIDTH, POSTLENGTH, forConstruction=True)
    .vertices()
  )

Each of those lines should be a gui tool interaction that generates that line of code.

Comment · 6 months ago

If there's too many lies, "source or gtfo" becomes more important

Comment · 6 months ago

Was hoping for a tournament bracket of best lies found in training data :(

Comment · 7 months ago

It's easy: bugs look icky. I wouldn't eat them. Grind them up out of sight and use them as an ingredient? Suddenly I'm fine with it.

Comment · 7 months ago

Helix editor is based around that. Better than vim default imo

Comment · 7 months ago

Off the top of my head, wouldn't it be super easy to expose lab rats to microplastics and measure results?

No way this isn't heavily studies by now.

Edit: found a whole meta-study in like 30 seconds of searching: https://www.frontiersin.org/journals/public-health/articles/...

Comment · 7 months ago

Sounds like you need to multiplex a terminal with a terminal multiplexer.

terminal multiplexer

term mux

tmux

Comment · 7 months ago

Comment · 7 months ago

No, it's just propagated mistakes. Same for lose and loose.

Comment · 7 months ago

With nothing off the table, that includes bans on Crocker's Rules, right?