When it comes to smart-contract blockchains, which are necessary to solve big complex problems, developers have a lot of choices: delegated proof-of-stake or proof-of-work, public or private, permissioned or permissionless, C++ or Solidity, etc.
Options are generally a good thing, unless it’s difficult to understand how to make a good choice or if a bad choice may result in a very expensive misstep.
Many of these options are artificially conflated and end up creating platform lock-in that is difficult to break.
It does not need to be this way.
Code should be code. Whether it is deployable on a platform is a negotiation between the platform and the developer. Essentially, if you’re familiar or comfortable with coding in Solidity or with the nuances of Ethereum smart contracts, you should not have to sacrifice your specific preferences to be a part of a different blockchain’s community.
Embracing interoperability means empowering the developers that didn’t adopt your preferred platform.
Blockchain interoperability.
Further Reading
1) Why Interoperability Is the Key to Future Innovation and Adoption
2) It Is Time for Blockchain to Prioritize Diversity and Inclusion