Tensorflow was also riddled with bugs, which worsened after Keras was made as default. Things didn't work as expected even in some regular cases. I switched to

Tensorflow was also riddled with bugs, which worsened after Keras was made as default. Things didn't work as expected even in some regular cases. I switched to Pytorch after I encountered this bug in a very normal use case back in v1.13 https://colab.research.google.com/drive/1D-kgD7NiRXTNTNwVr18H8C-edaL2zpqw#scrollTo=4Qxybq9yEHcy https://colab.research.google.com/drive/1D-kgD7NiRXTNTNwVr18... I've never encountered such a bug in Pytorch in the last 4-5 years.