@lerno is a ganedev himself so should be able to answer your question there Some links https://c3-lang.org/getting-started/ https://c3-lang.org/getting-started/design-goals/ https://c3-lang.org/faq/compare-languages/…
You can define your own "built-ins" types and functions(!) so that should make it indistinguishable. You can also extend the standard Library from inside your own project, modules are open for extension
True, C3 at least is one breaking release per year and between those there are non-breaking additions. It's quite common for a project to pin to a stable version so this doesn't seem too unpredictable.
Standardisation of code and examples across codebases is a nice result of this too. This makes the code easier to learn and share
@lerno is a ganedev himself so should be able to answer your question there Some links https://c3-lang.org/getting-started/ https://c3-lang.org/getting-started/design-goals/ https://c3-lang.org/faq/compare-languages/…
You can define your own "built-ins" types and functions(!) so that should make it indistinguishable. You can also extend the standard Library from inside your own project, modules are open for extension
True, C3 at least is one breaking release per year and between those there are non-breaking additions. It's quite common for a project to pin to a stable version so this doesn't seem too unpredictable.
Standardisation of code and examples across codebases is a nice result of this too. This makes the code easier to learn and share