The excessive amount of emdashes does seem to imply it's LLM slop ragebait. The prompt probably included "make intentional mistakes in your arguments to drive engagement" or something like that.

I haven't downloaded your model but https://www.i-solids.com/ (US-based, FDM and MJF) and https://www.weerg.com/ (Italy, mostly MJF ) will both do instant quotes and you might get reasonable prices from them at scale. PCBWay and JLCPCB in China will also do 3d printing at reasonable volume, if you want to get an idea of a baseline price.

I was quoted $73.19 from I-solids, just FYI

Thank you, I'll look into it.

Related self-promotion: I built pgtemp (https://github.com/boustrophedon/pgtemp) to automate doing exactly these mkdir/initdb/load/destroy steps.

Author of the blog post here -- that looks like exactly what I needed, so I'm probably going to add a dependency to it to https://github.com/kaaveland/eugene/ so I can delete a ton of code. :-)

That looks fantastic, so I'm actually just going to put a link to it in the post so that more people see it.

Thanks! Feel free to file an issue if there's something missing from the library or the daemon.

There's a similar JVM version here: https://github.com/zonkyio/embedded-postgres

It's well maintained and seems to do what it says on the tin. I start it up once across all the suites (managing DB state as required in the suite) and the overhead is very minimal.

I made https://github.com/boustrophedon/pgtemp to solve this for myself

i dont understand why everyone just doesn't do this unless they are working with really large volumes of test data. it literally takes a fraction of a second to mkdir, call pginit, and open a postgres socket.

idk if you've solved this, but PG doesn't like to bind to 0, so you have to manage ports. And I've had issues with processes sticking around if the test driver has crashed (I dont currently, but i'm turning off setsid in postgres).

My experience exactly - we use a JVM equivalent, and it's extremely fast to start up and reliable to use.

Start it once across a bunch of suites, and have each suite manage its DB state. Done deal.

Thanks for writing the blogpost! I think it's perfectly valid as a fun demonstration of the utility of the wayback machine.

The `parse_program` function is public inside the `bc_util::parser` module, and the parser module is marked public inside `bc_util`, but in the `calc/src/bc.rs` file the `bc_util` mod isn't public, and can't be accessed from a test inside the `tests/` folder, which only has access to the public API exported by the library.

There are several sites with instant quotes that are cheaper than Shapeways.

PCBWay and JLCPCB both offer similarly-priced very cheap 3d printing and CNC services out of China. Weerg in Italy also offers 3d printing and CNC services and I'm probably going to try them out for the next thing I need printed. The only non-marketplace service I've seen in the US that offers instant quotes is i-solids in Texas, but they have quite high startup costs and seem to be more geared towards small-medium production runs.

I'm not sure if it's related, but I have the git branch in my PS1 and I've noticed that it's much slower to show a new prompt when inside very large repositories now, and I don't think that was the case previously.

I built this weather forecast / todo list with the weather.gov and todoist APIs https://harrystern.net/halldisplay.html

Linux has seccomp and landlock, which are basically harder-to-use versions of pledge/unveil.

Someone has combined those things to port Pledge to Linux.

https://github.com/jart/pledge