That is def the first answer I was looking for 
Can you be more specific what you mean here? There is something that ink! can do regarding creating an app with multiple contracts that Solidity cannot do?
Starting to insert my own ideas:
Everyone in the ink! team must know about the proposed “merge”, which is trying to turn ink! into a language which can be used for both Contracts on Polkadot and Services / Parachains.
This seems to me to be the most obvious fit for where ink! would make sense in the Polkadot ecosystem. As the language that you can launch both a contract on the “Polkadot Hub” and a service compatible with “Polkadot Cloud”.
I think if ink! remains just an alternative contract language to Solidity for the “Polkadot Hub”, it seems very unlikely to take off or make a meaningful impact into adoption / growth of Polkadot.
Of course, in a bull market where we have plenty of successful teams and builders, such experiments could be okay, but I don’t think we are really in a position where Polkadot can afford to walk down paths like this with such little upside.
For example, any resources currently being used on ink! compatibility probably are better used on Solidity compatibility (if they were one to one), or even Move, which has some existing hold on the larger community already.
Anyway, I guess we will see how the treasury voters feel about putting money in directions like this.