Feeback on transifex native need for Open Source project

[eldy]

As invited by Nikos, i send you a feedback about transifex native for Open Source project.
You must know that in Open source world, major project succeed because they respect some rule. Among those rule, this one:

• Try to have code that does not depend too much of other libraries (use abstraction to be able to change at any time) or external services (try to use service that follows standard only and try to use them a way you can change them at any time).

It seems transifex is publishing its native tool as opensource so this is a good news. However, as Open Source leader of a lot of projects, i still prefer to use a simple sync my application language files -> transifex then a sync transifex -> application language files. The reason is that independency seems is better (if my understanding on how tranifex native works). What happen if we need to change the translation provider because transifex become suddenly no more free for Open Source project ?
For this reason I probably won't use "transifex native" for Open source project. But I will continue to use transifex... but from command line tool, because transifex is still a very good project and we really appreciate the help transifex provides to https://www.dolibarr.org project.

This is for my feedback.
And again, thanks for beeing free for Open Source projects.

[n1k0sv]

Thanks for the feedback @eldy, we can totally follow-up your reasoning behind OSS projects.

Our long term plan around Transifex Native is pushing the needle towards an OSS offering, both in the SDKs and especially for our CDS component so that we remove the strong coupling barrier with Transifex TMS and make OSS community feel safe.

We want to build a modern and exciting way to do localization in your apps and we want this to be as inclusive as possible.