XENA VS tabnine-vscode

At the moment this is available only on "stage" branch. https://github.com/zarkones/XENA

or directly to the code at https://github.com/zarkones/XENA

Meet XENA. github.com/zarkones/XENA Free as a free beer. My motivation for its creation was the fact that a lot of red team solutions are expensive. Like real expensive. Price could easily go up to 10,000 euros for a single user, one year license. That's too much for myself. Yes. I could use a software like Metasploit (free ver.), but with it I feel like I'm not learning much. Thus XENA is born, from community to the community. You can have a taste of how it looks here: youtu.be/e7ELtfbnvqI

Or at least an open-source red team operations oriented framework, wait, there is: github.com/zarkones/XENA

Both are related to limitations of vscode completion engine, so Tabnine can't really blamed for them in any way.

1. Initially Tabnine's auto-completion was triggered on any character, which best leveraged Tabnine's power but also had inherent problem: when Tabnine was triggered on non-letter character it sometimes prevented Vscode from showing suggestions from other completion sources (LSPs, snippets). There is a discussion in https://github.com/codota/tabnine-vscode/issues/6 with me explaining that the only viable solution is to reduce set of trigger characters to letters only. In the end a fix was pushed that reduced the set of trigger characters, which made the problem less likely but still not solved. The are numerous duplicates of this issue on Github.

2. Another problem is when Vscode has auto-completion suggestions from Tabnine and other sources (LSP, snippets), it frequently puts Tabnine's at the top of list. This is a big no-go for me because most of the time just want to complete the identifier (class field, method etc.). Modifying just the extension code didn't help so in the end I had add a small patch to Vscode itself, which gives lowest score to Tabnine's candidates: https://github.com/sergei-dyshel/vscode/commit/ee73034b9ec6c....

I must admit that both problems can be practically solved by new "inline auto-completion" mechanism in vscode which looks very promising for AI-based completion in general. I'm looking forward to evaluate it.