Viewing a single comment thread. View all comments

OutrageousSundae8270 t1_j5g2wm3 wrote

I don't think one guy saying "TensorFlow is on its way out" constitutes it reaching EOL lol

2

ContributionWild5778 OP t1_j5g35tl wrote

I thought so too but then a few people also mentioned the same thing in my office. And currently, I am working on 3D computer vision and all the git repos I found for it has pytorch as its framework I barely found any with TF implementation

1

OutrageousSundae8270 t1_j5g4152 wrote

One of the posters in that thread says "Google always struggled to build a long lasting ecosystems for their products", I don't even see how that is relevant anymore since TF has been open sourced and is not necessarily maintained by Google anymore.

PyTorch is more popular I concede that, but I don't think the people responsible for maintaining TensorFlow are going to shut up shop just because PyTorch is modestly more popular.

2

ContributionWild5778 OP t1_j5g4ck6 wrote

Oh, okay. Thanks a lot! The reason I don't feel like moving on to pytorch is because I am a bit comfortable in TF now. And I don't have the energy or time to learn a different framework right now.

1

OutrageousSundae8270 t1_j5g51tx wrote

I'm know the TensorFlow API really well considering I've been using it for about 2 years now.

I've used PyTorch before as well, its really not hard to learn the other once you're good at one of them.

PyTorch is a little more verbose than TensorFlow , e.g. TensorFlow has a default training loop that can be started by invoking the fit method where as in PyTorch you write the training loop yourself regardless, you always have to explicitly call methods for AD/Back propagation as well in PyTorch.

1