I did find that post AFTER my posting and cannot agree more. it APPEARS like …
The fundamental question, for me is still not answered. Is this deprecation the death of caffe2 or not? Is the migration path going to happen gracefully or rudely.
I do not know if the C++ used in PyTorch is completely different than caffe2 or from a common ancestor. I know it said it was “merging”. So architectural details may be helpful.
After my initial test with python on 5 or 6 different frameworks it was really a slap in the face to find how poorly c++ is supported. So far caffe2 looks best but then the red flag goes up on “Deprecation” and “Merging” and what that exactly means.
                  Has (recent)c++ prebuilts |  C++ buildable |   Handle PreBuilt Models |      HW Acceleration  |

MXNET                NO                               |  Not So Far      |        Yes                           |    Fastest Cuda  impl |
TensorFlow         NO                               | Not since change to bazel | The pgm is the model | Slower |
CNTK                    ?
caffe2                  Yes                              | Yes                   |   Yes lots of them               | yes |
libtorch                Yes                              | Yes                   |  Only TorchScript  |  Yes |
and non-cuda
OpenVino            Yes                              | Yes                   | Yes lots  | Yes, Intel only               |
Am I wrong about any of this assessment?
Forgive me “SLA” ???
Naming is trivail, just wanted to point out how that can contribute to the impression of poor c++ support, gets washed out by the plethera of python info.