dusk: rename the project to sysgpu #1092

New issue

Closed

opened 2023-10-28 00:19:00 +00:00 by emidoots · 1 comment

emidoots commented

2023-10-28 00:19:00 +00:00

(Migrated from github.com)

In light of https://github.com/hexops/mach/issues/1055 and https://github.com/hexops/mach/issues/1091 we will maybe rename Dusk to something else to clarify it's not the same thing we talked about in https://devlog.hexops.com/2023/mach-v0.2-released/#dusk-experimental-pure-zig-webgpu-implementation

Name suggestions are welcome, but ultimately I will decide

emidoots commented

2023-11-05 19:48:19 +00:00

(Migrated from github.com)

Decision made this morning

The perfect replacement name for Dusk came to me last night in a dream 🙂 I don't know why I didn't think of it before.

sysgpu

We already have an established convention to use sys when we have a low-level library which provides access to some topic from the system APIs, we have sysaudio for audio input/output, sysjs for WASM<->JS API calls, etc. (sidebar: I also propose we rename mach-objc to mach-sysobjc)

This is nice because it doesn't conflict with the existing mach-gpu repository, it isn't a 'brand name' (like Dusk is an arbitrary thing not describing what it does), etc.

Decision made [this morning](https://discord.com/channels/996677443681267802/1153411442813448254/1170797096249589941) > The perfect replacement name for Dusk came to me last night in a dream 🙂 I don't know why I didn't think of it before. > > `sysgpu` > > We already have an established convention to use sys<topic> when we have a low-level library which provides access to some topic from the system APIs, we have sysaudio for audio input/output, sysjs for WASM<->JS API calls, etc. (sidebar: I also propose we rename mach-objc to mach-sysobjc) > > This is nice because it doesn't conflict with the existing mach-gpu repository, it isn't a 'brand name' (like Dusk is an arbitrary thing not describing what it does), etc.