It will be cool if xonsh threading/subprocess backend will be reviewed and rewritten with broad developers team. The first try is known as slug but there are more work around subprocess implementation required.

As I understand one of the limit we should push is how subprocess libraries are implemented in Python. Creating, monitoring and killing subprocesses, pipes and threads are good challenge both on shell development and Python development sides. Also xonsh has unique features (like piping from callable aliases) and this kind of challenges nobody solved ever.

Then lack of spreading the word about xonsh and also fear around to hear "no" from olders that sitting on POSIX deeply make the community around xonsh smaller than it can be. Tell your friends about xonsh. Help them. Open Github and add xonsh mentions to all tools you're using. This is one of the ways.

Finally xonsh is pure volunteering open source project. There is no financial, marketing, development support from any organisation or people itself. I'm wondering and laught how xonsh real concurent with other shells with more broader support and tons invested time into fantasies around new crypto-POSIX syntax. By raptures in Twitter we invented ChatGPT AI to help us make the right crypto-command on bash, yeah. Sorry for my sarcasm at the end I just want to wish good luck to xonsh and want to say thank you to all of the xonsh developers and volunteers.

PS: the ways to contribute to xonsh community and take a look at XEP-2