Multiple implementations of toon in the same languages

[4ndre4s]

Recently, more and more implementations of toon written in different programming languages have been appearing. I welcome the huge interest in toon in general and appreciate the work of those who implement toon in various languages.

However, I am not sure if it is necessary or beneficial to have multiple implementations of toon in the same language (So far I have spotted python, golang and rust).

Main questions:

• Where is the difference between the implementations and where is the individual benefit? Who is the audience?
• If the reasons are related to performance or package size, might that be something that could be improved in the existing implementation, rather than creating a new one? Do these two criteria have such a high priority or should we use the time and effort to focus on improving toon itself?
• Who is going to maintain all the packages in the future? Might unmaintained implementations have a negative impact on toon?

[felipestanzani]

I agree. The developers should unite and make the open source projects get traction instead of creating concurrent versions of the same thing.

[johannschopplich]

Hi @4ndre4s and @felipestanzani, I completely agree with your concerns. Multiple implementations in the same language this early creates confusion and fragments effort. Thanks for raising this. 🙏

I've just opened discussions to bring authors together:

• Python (3 implementations): https://github.com/johannschopplich/toon/discussions/54
• .NET (2 implementations): https://github.com/johannschopplich/toon/discussions/55

The goal is to create official implementations under the toon-lang organization with co-maintainers, clear ownership, and sustained support. My repo would move as well, of course.

[johannschopplich]

@felipestanzani I'd love to have your Java implementation on board as well!

[felipestanzani]

My honor to help.

[shahshlok]

Hi everyone,
I love the toon format and its use case for LLMs, and I see that there is already work happening on the Python SDK.

Id like to know how to contribute to it? I can learn anything and everything that is required to catch up to speed

[johannschopplich]

I'm currently contacting library authors to contribute to the ecosystem by either:

• moving their repo to the TOON org
• being part of the Team for the given language implementation

Closing this discussion for now.