Self-Contained Executable Programs with Deno Compile

10 pointsposted 2 days ago
by soheilpro

3 Comments

jorrdang

2 days ago

Has anyone figured out cross compiling for macOS targets from a non-macOS host? For example, executing `deno compile` in a Jenkins job in a CI/CD workflow? I’ve tried numerous times and get stuck on the macOS target not passing Apple’s security rules. The codesigning example in the blog post is something I’ve tried but I feel like I’m missing something.

evnix

a day ago

Small binary size?

58MB for a hello world doesn't not seem small to me.

58MB might not seem much but we used to have entire games in a few MB.

You might argue it doesn't increase that much after 58MB, I don't know what is this good for. I want my command line apps to be lean, I don't care about decoupling source and deno binary on a server side program. I don't see the benefits personally.

zen928

a day ago

this is a bit of a mischaracterization of what's being claimed in the post, all they were saying about binary sizes is that their updates have resulted in SMALLER binary sizes when compiling compared to the previous versions, i.e. they're noting an improvement. nowhere on this page nor any linked from it do they claim they make "small binaries" (that i can find! could be wrong), and you even had to click through their example dedicated to noting this improvement to find the 58mb number you keep mocking.

if you wanted to argue that point, I'd suggest you compare the other solutions that exist today to compile nodejs projects into single executable binaries to be able to have a discussion on why you consider their progress lacking. it's a reasonable point that disqualifies a lot of use cases for these types of tools, but I don't think the conversation was framed from that perspective.