this post was submitted on 13 Dec 2025
45 points (88.1% liked)

Programming

24348 readers
218 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 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
UlrikHD@programming.dev
45
What's the point of lightweight code with modern computers? (liam-on-linux.dreamwidth.org)
submitted 4 weeks ago by codeinabox@programming.dev to c/programming@programming.dev
28 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] Ephera@lemmy.ml 5 points 4 weeks ago

Runtimes/“VMs” like the JVM also allow nice things like stack traces. I don’t know about the author but I much prefer looking at a stack trace over “segmentation fault (core dumped)”. Having a runtime opens new possibilities for concurrency and parallelism too.

Rust has stacktraces without needing a runtime. Don't ask me what exactly is going on behind the scenes, but there is a way to request a stacktrace for a given point in the program. And unless you're doing embedded stuff, a stacktrace is automatically generated for errors.

And as for concurrency/parallelism, it's correct what you wrote, but I just wanted to point out that it doesn't have to be a language runtime. Using Rust as an example again, you typically spawn the Tokio async runtime on program start, if you're gonna do async/await stuff.