11–20 of 45 posts
"RNNCell objects now subclass tf.layers.Layer. The strictness described in the TensorFlow 1.1 release is gone: The first time an RNNCell is used, it caches its scope. All future uses of the RNNCell will reuse variables from that same scope. " I'm so glad they fixed this, I've been running 1.0 for the last few months because the 1.1 release broke their own RNN tutorials and a lot of seq2seq code that is out there. I r…
Did they explain why they decided to stop supporting GPU for Mac OS X? That's going to make a lot of developers think twice before upgrading.
Did they explain why they decided to stop supporting GPU for Mac OS X? That's going to make a lot of developers think twice before upgrading.
Sounds like a lack of external contributors maintaining it to me, are there really that many users? Everyone I know on macOS uses docker (or some other virtualisation) to run linux for small jobs and then connects remotely to linux boxes when they need more computing power.
"RNNCell objects now subclass tf.layers.Layer. The strictness described in the TensorFlow 1.1 release is gone: The first time an RNNCell is used, it caches its scope. All future uses of the RNNCell will reuse variables from that same scope. " I'm so glad they fixed this, I've been running 1.0 for the last few months because the 1.1 release broke their own RNN tutorials and a lot of seq2seq code that is out there. I r…
What is exciting about it, do you think?
Did they explain why they decided to stop supporting GPU for Mac OS X? That's going to make a lot of developers think twice before upgrading.
Site is desktop only: "Oops. Since this experiment loads over 14,000 bird sounds, you'll need to view it on a desktop computer."
Did they explain why they decided to stop supporting GPU for Mac OS X? That's going to make a lot of developers think twice before upgrading.
> TensorFlow 1.1.0 will be the last time we release a binary with Mac GPU support. Going forward, we will stop testing on Mac GPU systems. We continue to welcome patches that maintain Mac GPU support, and we will try to keep the Mac GPU build working. Sounds like a lack of external contributors maintaining it to me, are there really that many users? Everyone I know on macOS uses docker (or some other virtualisation)…
Did they explain why they decided to stop supporting GPU for Mac OS X? That's going to make a lot of developers think twice before upgrading.
> TensorFlow 1.1.0 will be the last time we release a binary with Mac GPU support. Going forward, we will stop testing on Mac GPU systems. We continue to welcome patches that maintain Mac GPU support, and we will try to keep the Mac GPU build working. Sounds like a lack of external contributors maintaining it to me, are there really that many users? Everyone I know on macOS uses docker (or some other virtualisation)…
Unofficially, there may be some people using Hackitoshs with rather beefy GPUs for machine learning.
There's a lot you can do easily on a $500 GPU that should take too long on CPU. And I prefer the shorter write/run/debug loop of working locally. It's the same niche other machine learning workstations fill, only with the preferred desktop OS.
There will also be external GPUs for Macs soon(ish), and those would be perfect for tensorflow. I'm not sure at that point they'll want it running on Macs again, and discontinuing support now may be the wrong decision.
Earlier quoted context omitted.
> TensorFlow 1.1.0 will be the last time we release a binary with Mac GPU support. Going forward, we will stop testing on Mac GPU systems. We continue to welcome patches that maintain Mac GPU support, and we will try to keep the Mac GPU build working. Sounds like a lack of external contributors maintaining it to me, are there really that many users? Everyone I know on macOS uses docker (or some other virtualisation)…
It just means OSX users (like me) have to compile from source - no different from PyTorch. Happy to provide compiled binaries for 10.12, though it's a bit of a chore to get Xcode clang and CUDA to play nice together.