The little-known discordant projection

Thank you for your honesty. In my experience when people blame Linux for their problems, it’s usually projection.

I guess in contrast cannot be called into.

Natural next step after the vacuum tube

bsky.app/profile/elfp...

What prints if you press the red printer button

(This says to me even *if* we get all the dynamic requires sorted there will still be issues with these kinds of libraries)

I think it's possible to get there, someone is going to have to mind-meld with the runtime and bun to do it.

I have another experiment going to see if I can get github.com/Automattic/n... to be bundled into the binary (which is how the image library works).

Currently that's ending somewhat sadly.

Copy/paste error in the link above fixed here

github.com/jpolitz/pyre...

Ah nice thanks.

I should have said I got nerd-sniped into going through this exercise this morning (github.com/jpolitz/pyre...), even up to saving an image to disk.

Then I moved the binary and it stopped working. We have dynamic requires and they still poke around in node_modules.

And just to confirm, a simple js program that just logs does produce a binary with sensible behavior using the same command, so I don't think I'm goofing on the basic thing to try :-)

(The last command prints nothing)

At least on my system, the doing the most straightforward thing has no error messages but creates a binary that doesn't produce any output at the terminal (running the compiler blob with `node` and no arguments should print the usage).

At a glance that page says “All built-in Bun and Node.js APIs are supported.” which is actually more than Node's support at the time I tried (only supported a subset), but Pyret has a fair amount of surface area these days.

Would love more expertise and input here.

This would be great. I went down the rabbit hole of node's support for this for a few days. It's a so close/so far thing.

For example, we use node-canvas and other similar packages to get the image library to work headless, and they rely on a pile of C code, which complicates things.

For users who are savvy devs, it's probably better to just npm install pyret-npm as a dependency of the project, and then all the node_modules are local to the working directory and run with `npx pyret ...`

Thanks. This is probably fixable by using `require.resolve()` appropriately, and is needed for different --install-strategy settings to work.

We need something like the symlink if we want pyret to work as a global command because we want to generate standalone JS blobs runnable with plain `node`.