Earlier quoted context omitted.
Few people use PyTorch largely because it is relatively new (0.1.12). It even doesn't have distributed training capabilities (coming in 0.2). Your arguments don't say anything about frameworks themselves. It is unfair! When people say PyTorch is better for research, they mean it is more flexible, and it is easier to implement non-trivial network architectures with it, such as recursive network, which is a cumbersome…
All of these frameworks are "relatively new". TensorFlow: 1.6 years. CNTK: 1 year. PyTorch: 0.5 year. Are they really impossible to compare? > When people say PyTorch is better for research, they mean That's not what "people" say. They tend to say the opposite. Maybe we can ask OP what he meant when he said it. > it is easier to implement non-trivial network architectures with it, such as recursive network It is inte…
1.6 years is a long time in DL community.
> That's not what "people" say. They tend to say the opposite. Maybe we can ask OP what he meant when he said it.
Go ahead! Ask it.
> They use Chainer and DyNet.
You know Chainer came far before PyTorch, which heavily influenced PyTorch's design. You are always saying XX is using XX. Why not talk about frameworks themselves?
If you insisted to your idea, let's settle down. I don't want to start a framework war. I just want all frameworks to be equally considered.