You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed @peterbraden in another issue, here a new thread is used to discuss the SWIG interface. Just move the discussion of SWIG interface here, separating from another thread.
The text was updated successfully, but these errors were encountered:
what if subsets of tensorflow were initially rewritten in native javascript - for a proof of concept?
I'm not sure what the performance differences would be - or level of difficultly - writing the algorithms in javascript vs SWIG interface. I assume some % of tensorflow can be written in javascript - but I haven't gone through the all source code understand what's happening.
I do believe tensorfow is one of the most significant libraries published to date - so bridging the gap w/ JS would probably increase it's utility and usage by an order of magnitude or more. It only needs to be performant enough to be useable - and I'm certain a node-tensorflow has the potential to be far more performant than the python code.
As discussed @peterbraden in another issue, here a new thread is used to discuss the SWIG interface. Just move the discussion of SWIG interface here, separating from another thread.
The text was updated successfully, but these errors were encountered: