4 ms·
(OP, please don’t subject yourself to TensorFlow/Keras. The moment Jax became available on TPUs publicly, the moment I stopped using TF. And boy oh boy, “never
by sillysaurusx 5y ago
(OP, please don’t subject yourself to TensorFlow/Keras. The moment Jax became available on TPUs publicly, the moment I stopped using TF. And boy oh boy, “never looked back” is an understatement. I still cringe remembering all the time I spent trying to get tf.function to just please, please work, like a housewife alarmed that neither her partner nor herself are able to actually work.)
- m3at 5y agoTo support your point with data, here is a graph of usage of TF vs PyTorch in papers over time: https://horace.io/pytorch-vs-tensorflow/ https://horace.io/pytorch-vs-tensorflow/
- cweill 5y agoI've seen this chart too. But research != Production. I bet that TensorFlow is still more commonly used in serving than Pytorch because of great tooling like TensorFlow Serving. I could be wrong though, as I'm not up to date with the latest in the Pytorch ecosystem.
- dbish 5y agoFWIW PyTorch has TorchServe nowadays which does the same thing as TF Serving.