-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roadmap of node-tensorflow #15
Comments
@bryanerayner |
I wonder why Google don't release a Node compatible version. |
@bryanerayner I agree that JS streams or rxJS are well suited. Single value returns can always just return an array, or preferably an object. Alternatively, ES6 syntax has exactly what you're looking for (which runs fine in Node without precompiler) https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment In python you might return 2 values in a tuple. In JS you'd just return the array and use destructuring assignment.
|
You know, I hadn't thought about how destructuring was essentially the Python tuple syntax. Thanks for that. |
It would seem to me that there's the possibility of an "intermediate" C++ library that would implement some amount of the current Python-only code, and then idiomatic ES2016 bindings atop that. For running a network, there should be a pure-JS version so we can do browser-side intelligence. |
Just getting started looking at this. I was attempting to use TensorFlow earlier, but was severely hampered by the Python-only API. (Translation: I have too much on my plate to learn how to use another web framework in another language, just to play around).
That said - It appears to me that most of the difficulty here, is that the C++ API does not contain the full functionality that the Python API provides, and we might need to duplicate a lot of logic in order to implement the full level of capability in this module.
I am wondering, if this almost is a blessing in disguise, since
numpy
in the Node world, and Python range comprehension is nothing like what we (don't) have in Javascript.I think a re-envisioning of the Python API will be necessary to turn this into a truly useful module, so perhaps it shouldn't be avoided.
The text was updated successfully, but these errors were encountered: