I had Racket TensorFlow bindings as a possible-TODO for me, but I don't
yet know ML tools I'll use, and what APIs/layers I'll prefer atop tools
that offer more than one.
(One of the reasons to play with ML in Python initially: almost
everything has Python APIs, at the moment, and some of the most popular
ML tools are written substantially in Python rather than being a veneer
of bindings.)
Also, some toolkits might make more sense to call from Racket through
something other than the current Racket FFI.
(For example, Python ones, or C code you don't want to risk stomping on
your Racket code, and might not even be open source. Also, there's also
a good chance that you're running non-ideal vendor-specific GPU compute
libraries and drivers right now, though hopefully that will soon improve.)
--
You received this message because you are subscribed to the Google Groups "Racket
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
