# TensorFlow

20 Hacker News commenters recommended TensorFlow and 36 criticized it, November 2025 to November 2026. It was recommended in 10 of 13 months.

**Verdict:** Early end-user machine learning library, pivotal to fast AI development and widely used. Critics cite hard debugging, breaking changes between versions, and losing ground to PyTorch.

## Why people recommend it

- Pivotal to fast AI development (2 comments): "libraries like TensorFlow which were pivotal to fast development of AI" ([source](https://news.ycombinator.com/item?id=48005163)) "pytorch and tensorflow were also there to facilitate this" ([source](https://news.ycombinator.com/item?id=46355440))
- Widely used across ML projects (2 comments): "at least it's one tons of people use" ([source](https://news.ycombinator.com/item?id=49220029)) "we got tensorflow, pytorch, gpgpus" ([source](https://news.ycombinator.com/item?id=47904875))
- Open-source, scalable deep learning framework (2 comments): "the lego-like aspect of NN that enabled scalable OSS DL frameworks" ([source](https://news.ycombinator.com/item?id=47898316)) "Pytorch didn't have to be FOSS, nor Tensorflow." ([source](https://news.ycombinator.com/item?id=47053477))
- Competitive, excels in some use cases (2 comments): "very capable products, that compete very well in ML space" ([source](https://news.ycombinator.com/item?id=46080911)) "Each of these libraries excels for different use cases." ([source](https://news.ycombinator.com/item?id=46436600))

## What people warn about

- Hard to debug static graphs (5 comments): "The inability to use print debug to tell me the dimensions of my hidden states was 100% why TF was hard" ([source](https://news.ycombinator.com/item?id=45846483)) "Their bet on static compute graphs made writing code verbose and debugging difficult." ([source](https://news.ycombinator.com/item?id=45844251)) "Tensorflow didn't have that at the time which made debugging practically impossible." ([source](https://news.ycombinator.com/item?id=45844255))
- Breaking changes across versions (3 comments): "It's the Tensorflow strategy; deprecate the old version while the new version still doesn't support all the old one's functionality." ([source](https://news.ycombinator.com/item?id=47079745)) "Not being able to load previously trained models with a new version of the library is wildly painful." ([source](https://news.ycombinator.com/item?id=45849820)) "They killed TF1, upsetting those users, while not having a fully functioning TF2" ([source](https://news.ycombinator.com/item?id=45844737))
- Losing ground to PyTorch (3 comments): "let TensorFlow lose researcher mind share to PyTorch, and caused Google fragmented landscape across TensorFlow and JAX" ([source](https://news.ycombinator.com/item?id=49186109)) "Tensorflow is largely dead, it's been years since I've seen a new repo use it." ([source](https://news.ycombinator.com/item?id=47206134)) "years later PyTorch ate its lunch, which they eventually admitted with TF 2.0" ([source](https://news.ycombinator.com/item?id=49193759))

## Alternatives hackers recommend

- [PyTorch](https://hackerapproved.com/p/pytorch.md): 131 recommend
- [MLX](https://hackerapproved.com/p/mlx.md): 75 recommend
- [JAX](https://hackerapproved.com/p/jax.md): 49 recommend
- [OpenCV](https://hackerapproved.com/p/opencv.md): 46 recommend
- [tinygrad](https://hackerapproved.com/p/tinygrad.md): 40 recommend

## Cite as

Hacker Approved, "TensorFlow", https://hackerapproved.com/p/tensorflow/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).