4 ms·
Not trying to start a language war, but I would like the old or the new api better if it had static types. Right now it's thousands of functions that can take t
by maaaats 8y ago
Not trying to start a language war, but I would like the old or the new api better if it had static types. Right now it's thousands of functions that can take thousands of different objects, and I would never know what to use except the few I randomly learned in a tutorial.
- me2too 8y agoBut the API is strictly statically typed in reality. The core is written in C++ and every operation requires a well-known type in input. As you can see from the error raised in this example: https://pgaleone.eu/tensorflow/go/2017/05/29/understanding-tensorflow-using-go/#question-time-1 https://pgaleone.eu/tensorflow/go/2017/05/29/understanding-t...
- halflings 8y agoThen you'll be happy to learn about Swift for Tensorflow: https://www.tensorflow.org/swift/ https://www.tensorflow.org/swift/ And no.. it's not simply a Swift wrapper for tensorflow, it's literally Tensorflow (or generally speaking: differentiable calculation graphs) built into the Swift language.
- lostmsu 8y agoMy company is working on a full API .NET binding. Leave your email if you're interested in trying the first technical preview in about 2 months.