Re:Covariant.ai and applying deep learning to robotics
by Koshkin on Wednesday May 06, 2020 @07:30PM
(#23097715)
Meta/off-topic: I think that for many people the use all these cool-sounding "mathy" names - covariant, differential, tensor (flow), etc. may in fact be more irritating and confusing than justified to any meaningful degree.
[ Parent
| on HN ]
Re:Covariant.ai and applying deep learning to robotics
by ProjectBarks on Wednesday May 06, 2020 @09:18PM
(#23098578)
Cough... y combinator... https://en.wikipedia.org/wiki/Fixed-point_combinator#Fixed_p...
Re:Covariant.ai and applying deep learning to robotics
by unishark on Thursday May 07, 2020 @12:07AM
(#23099617)
I like mathy company names. In fact, as a math person from long before it was cool, I love that others like them too now. I still own a few mathy domain names that friends warned me against using years ago when I was deciding on the name of startups. Maybe their time has come.
What does irk me a bit is when programmers abuse math words. Like implementing correlation and calling it convolution. Or using Tensor to describe a nested array of numbers. Sort of like nerdrage over an inauthentic movie portrayal of a comic.
But Tensorflow otherwise is just kinda descriptive. An iteration of the "dataflow graph" idea that operates on "tensors".
Re:Covariant.ai and applying deep learning to robotics
by sgillen on Wednesday May 06, 2020 @08:15PM
(#23098113)
What’s wrong with using mathy names to describe mathy products?
Re:Covariant.ai and applying deep learning to robotics
by whatshisface on Wednesday May 06, 2020 @10:52PM
(#23099173)
It's annoying when the products aren't what the names describe. It would be like naming a brand of facial tissues "Motor Vehicle" or a brand of computers "Apple." ;)