Create ecosystem-guide.md

[kvark]

I haven't put too much effort into updating this. Feel free to discard.
Wanted to see if we could have something along the general direction produced by the group.

[cedric-h]

I know you're trying to keep your descriptions of the libraries very catchy and concise, but when I think three-rs I think "prototyping/generic rendering needs" and not necessarily "fancy".

Then again, you're a maintainer on the project -- so if that's the direction that you want to take it in, I understand.

[Ralith]

"Raw" is strange word choice here when e.g. ash (and gl-rs?) are much thinner.

[kvark]

Thank you for the feedback!
I think the attempt to make this funny and catchy is inappropriate, and I need to reshape the document into something serious and more descriptive.

[AlexEne]

I think "ecosystem status" is a better description rather than an "ecosystem guide".
It also aligns a bit more with the not endorsing libraries part and it becomes a here's the landscape type of document.

[Lokathor]

Funny and catchy is good, please don't think that we don't want some levity in the documentations and guides.

It's just that it's also a first draft as you said, and so we want to provide some fix ups about the accuracy of the document content in between the jokes.

Particularly with a gamedev working group, light and a little humorous is definitely the right general tone to have by default.

[kvark]

Possible home choices for this:

• a document here
• a wiki page
• a page on "arewegameyet" (cc @doppioslash)
• nowhere

[kvark]

ok, here comes another silly attempt to make it sound like fun. If that doesn't turn out to be good, I'll rewrite it to be formal and boring :)

[Lokathor]

Good start! I like the list, but I think we should also beef it up with a little more detail about each item as we go.

If I have time this evening I'll try to write some stuff and then PR that onto your branch so that it merges into this PR here. Does that sound like a good way to use git? I've never done it like that so I don't know if that's usually done, i just sorta thought "that should work right i guess".

[kvark]

Yeah, that should work. Thanks!

…

On Aug 8, 2019, at 17:16, Lokathor ***@***.***> wrote: Good start! I like the list, but I think we should also beef it up with a little more detail about each item as we go. If I have time this evening I'll try to write some stuff and then PR that onto your branch so that it merges into this PR here. Does that sound like a good way to use git? I've never done it like that so I don't know if that's usually done, i just sorta thought "that should work right i guess". — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[JeanMertz]

Any reason why Rendy isn't on this list @kvark?

I'm glad this list exists, I've been trying to figure out what crate to start using for my "handmade game" (manually doing low-level stuff), and I've been thinking it'll either be Rendy or gfx-hal, gfx-hal is very boilerplaty (and very unsafe). Rendy seems to be still fairly low-level, but more Rust-y, right?

[Lokathor]

Well, rendy is the renderer of Amethyst, so it's "kinda" on the list, but it could use an entry of its own I suppose. I'll note that if I get around to writing stuff for this.

also of note so i don't forget, we should mention arewegameyet and try to put our ecosystem guide in context with that site in some way. we can say "this list is more curated, based on actual fitness of each crate for immediate use" or something like that perhaps.

[distransient]

Rendy the crate is not the renderer of Amethyst. The renderer of amethyst is the Amethyst subcrate amethyst_rendy which uses Rendy. Rendy itself is more of a rendering framework (hence the title "rendering engine" in the repository's description), providing important vulkan-like (the best way to describe gfx-hal lol) renderer constructs (some for improving safety) as described in its readme. You still gotta figure out how to print out your personal boat load of triangles on your own.

[kvark]

Rendy should definitely be in the list. It's quite unlike the other libraries though... in a sense that it's not a single library but a combination of helper libraries. We could list it near "wgpu-rs", "vulkan" and friends, or we could list "gfx" and "rendy" in a separate section ("travel with a tent?" :)).