# RFC 0025: Modern Process Spawn API

**URL:** <https://forum.crystal-lang.org/t/rfc-0025-modern-process-spawn-api/8773>\
**Category:** Crystal Contrib\
**Tags:** rfc\
**Created:** [March 10, 2026, 10:19am UTC](https://forum.crystal-lang.org/t/rfc-0025-modern-process-spawn-api/8773 "2026-03-10T10:19:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![straight-shoota](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/straight-shoota/32/36_2.png) [@straight-shoota](https://forum.crystal-lang.org/u/straight-shoota)\
**Post date:** [March 10, 2026, 10:19am UTC](https://forum.crystal-lang.org/t/rfc-0025-modern-process-spawn-api/8773/1 "2026-03-10T10:19:57Z")

</div>

This RFC is already pretty advanced, but may need some polishing: [RFC 0025: Modern Process Spawn API by straight-shoota · Pull Request #25 · crystal-lang/rfcs · GitHub](https://github.com/crystal-lang/rfcs/pull/25)

Here is the full proposal text. We’re still debating some of the hardest decisions in software engineering: naming things. Any input is appreciated.

> <https://github.com/crystal-lang/rfcs/blob/rfc/process-spawn-api/text/0025-process-spawn-api.md?rgh-link-date=2026-03-03T10%3A39%3A12Z>