3 ms·
I feel it's a bit unfair to criticise changes in a product at the leading edge of the most dynamic field of software. It's also slightly ungrateful for such a v
by matt4077 8y ago
I feel it's a bit unfair to criticise changes in a product at the leading edge of the most dynamic field of software. It's also slightly ungrateful for such a valuable addition to OSS–and I say that even though I tend to consider this argument overused.
But mostly I don't believe such criticism has much of chance of changing anything: The creators are already the most qualified you could have working on it, and it's unlikely they intentionally made mistakes in the early rounds of API design. Maybe it would have helped to spend a few more weeks on specifications rather than coding but, again, I wouldn't feel very comfortable second-guessing Google's project management.
I think the most likely outcome if such complaints start to pile up would be future projects just remaining proprietary, either longer, of completely.
- LeanderK 8y agoI really don't think so. Google doesn't make keeping up with tensorflow hard because of all the wonderful innovations, but because of needless breakage. Moving of packages, renaming things. It regularly breaks not-so-old code. Also, I don't think I am ungreatful. It's a serious criticism of a software i use almost daily. I really don't consider tensorflow to be great or even some kind of software, but for some tasks it's the only option. Also, google profits a lot from releasing tensorflow into the wild. But, all in all, tensorflow 2.0 seems like a step in the right direction.