Renaming to Testcontainers Native?

[oleg-nenashev]

I consider changing the project name. Should it be "Testcontainers for C/C++"? Or would it make sense to make it "Testcontainers Native" or another more generic name, and keep the "Testcontainers for C/C++ " for binding libraries which are likely to be many if the project keeps evolving? Any feedback is welcome!

As the roadmap states, In the future, I want the project to have proper C++ bindings, and I guess the Swift ones would find users too. Same for other advanced cases like MATLAB, and other languages that can include native shared libraries (E.g. R/Delphi/Perl and many others).

Testcontainers reach as a native binding

Tasks

Preview Give feedback

1. Rename the project to Testcontainers Native #34
   enhancement +1
2. Rename the Slack channel
3. Update documentation and links

[oleg-nenashev]

Feedback from the Slack discussion:

@kiview :

Would something like "Testcontainers Native Bridge"or "Testcontainers Native Adapter" make sense, since it provides this layer between the native interfaces of the different languages and tc-go?

@xtremekforever :

I like Testcontainers Native. It sounds better than saying Testcontainers C/C++ since it can be used from any language that supports native bindings 🙂

[oleg-nenashev]

After some consideration, I will continue with rebranding to Testcontainers Native, with a proper description and references to what it is designed for. Should there be competing implementations (e.g. like one that is happening for Swift now), I will make sure to have it documented on the language solution page, as a preferred "language native" solution

I will keep the logo as is for now, because C bridge will remain at the core for other implementations

[oleg-nenashev]

[oleg-nenashev]

After #39 , it is completed