search

kaitai-io / kaitai-io.github.io

Kaitai Project homepage
6 stars 9 forks source link

Add missing runtime libraries and mark them as WIP #11

Closed generalmimon closed 3 years ago

generalmimon commented 4 years ago

@GreyCat As suggested in https://github.com/kaitai-io/kaitai-io.github.io/pull/7#issuecomment-586921298:

And we should maybe also update the list: runtimes for Go, Nim, Rust and Swift are missing.

Also makes perfect sense. Let's add these clearly labelled as work-in-progress — that will both raise the image and assist in people's finding others work before starting their own?

However, it's not clear where is the boundary between the "normal" ready-to-use runtime and the one with the status work-in-progress. Rust and Swift runtimes are clearly WIP, but both Go and Nim currently pass ~70% of our tests, which basically means that it's quite usable even in production, if one doesn't need advanced (e.g. circular) imports or validation checks. So maybe we could remove the wrench icon next to those two.

GreyCat commented 4 years ago

So far, if we're talking about homepage of the project, the rule of thumb is that I've used was if the language support was included in the latest release (0.8 as of now, or 0.9 when it will be finally released), then we announce it — otherwise we're not advertising in on https://kaitai.io/

Officially, 0.8 includes: cpp_stl, csharp, go, graphviz, java, javascript, lua, perl, php, python, ruby.

If a language included and it didn't pass, say, 70% test mark back then, then we're claiming it's work-in-progress. Only go was in that category.

If we want to announce work on more languages — that's fine, let's just get them to some release. It makes very little sense to tease people with some sort of yet-unreleased thing.