Paul Moore

Public Key

npub16namardggju3sk47ndk89uy5u3a3mmdlkkj3uakw6sh9r89xqz7q8498m2

NIP-05 Address

Profile Code

nprofile1qqsdf7a73k5yfwgct2lfkmrj7z2wg7caaklmtfg7wm8dgtj3njnqp0qpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dspj3x84

Publishing to

relay.snort.social

relay.damus.io

nos.lol

Author Public Key

npub16namardggju3sk47ndk89uy5u3a3mmdlkkj3uakw6sh9r89xqz7q8498m2

Show more details

Last Notes

2024-09-08 21:31:27 UTC

- reply

As a user, I don't care about build time deps. Why do you? Remember, in the use case I'm talking about I don't want or need the distro to package the code.
But if you choose to package the app anyway, how is it different whether the code is in a dependency or part of the project itself?

2024-09-08 21:05:51 UTC

- reply

IMO there are two very different use cases involved. For some things, I just want the program to be there and I'm happy for my OS/distributor/package manager to deal with it. For other things *I* want to be in control. I don't want a packaged version, I want to get the version I want, when I want it.
It's for that second use case that single-file binaries are ideal.

2024-09-08 10:22:13 UTC

- reply

Thinking some more about it, my *real* point was that "a single executable you can just download and run anywhere" is the actual compelling argument for Rust. They deliver that by default, other languages require you to jump through varying levels of hoops to even get close to it. And yes, I know, static linking vs dynamic and security - but end users really only care about "can I download and run it?"

2024-09-07 11:08:16 UTC

- reply

Agreed, this is the killer advantage of *any* compiled language over one with a runtime. And to make it worse, Python is far from being the best runtime based language for app deployment :-(