this post was submitted on 06 Jun 2026
12 points (100.0% liked)

Programming

27213 readers
508 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev
12
What type of program should this be? (lemmy.world)
submitted 3 days ago* (last edited 3 days ago) by AstroLightz@lemmy.world to c/programming@programming.dev
11 comments fedilink hide all child comments
 

Let's says you want to make a program that takes user input and follows the CRUD structure for some data. This program would be executed from the terminal and wouldn't be used in any other projects.

If this program was made in a language that supports creating packages for other programs (e.g. Python, Rust, NodeJS), should this program be a 'package', or should it be a standalone program that has a simple "setup" script?

Assume this is a CLI/TUI app that runs in a Linux terminal.

EDIT: I'll provide some more details since it seems I was too vague:

This program would allow the user to create 'Script' objects that would be saved to a file on their system. These objects would contain metadata such as a name, the command to run, and a description.

These Script objects would only be used by this program, and by the user. (i.e not a system program)

you are viewing a single comment's thread
view the rest of the comments
[–] Ephera@lemmy.ml 1 points 3 days ago

Coming at it from the Rust ecosystem, I'd primarily opt for uploading release binaries somewhere. You don't particularly need a setup script, since Rust programs are generally self-contained.

Publishing a package in addition to that really isn't hard, but would be my secondary choice, since users are not likely to have cargo on their system.
Well, and cargo compiles on the target machine, which is great for supporting unusual architectures, but you may have C libraries included where it's just a gamble whether you can compile them on a given target system.