this extension was there before and also has some different implementations on a few things, I think just trying it out and comparing using them will make it obvious

One very important thing that will always be different is also the license.

This repo is clearly Public Domain via Unlicense while cpptools' is not 100% clear but points to MS License with nasty stuff like

You may only use the C/C++ Extension for Visual Studio Code with Visual Studio Code, Visual Studio or Xamarin Studio software to help you develop and test your applications.
You may not share, publish [...] the software, or provide the software as a stand-alone hosted solution for others to use.

So don't dare to copy the mscode.cpptools.vsix around - I just did it with this extension, sharing it with multiple colleagues.

Licence is a good point, because the MS C++ extension is (I believe) not legally compatible with editors such as vscodium, whereas this repository has no such problems.

I haven't checked the cpptools because of their license much, but I think the SSH debug on the different machine (= not attach via gdbserver) may not be available there. It is a very cool feature that allows you to debug for example on linux from a windows machine, something that plain gdb can only do if you configured it with a target for this [or I may be completely wrong about that feature]...

So the main question is: How do users want to have it documented (I guess in README.md but have no clue about the How)?
Maybe someone can create a PR for this?