You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Both Theano and CNTK are out of development. Meanwhile, as Keras backends they represent less than 4% of Keras usage. The other 96% of users (of which more than half are already on tf.keras) are better served with tf.keras. Keras development will focus on tf.keras going forward.
Importantly, we will seek to start developing tf.keras in its own standalone GitHub repository at keras-team/keras in order to make it much easier for 3rd party folks to contribute. Keras has never been moving faster than now :)
I want to contribute
Great decision! This will make it easier for contributors, but it also reduces confusion for users. Moving forward, will Keras only be tied to TensorFlow or will you experiment with newer backends such as Julia or Swift?
For the time being, it will be TF only, but I would expect that we will see new implementations of the Keras API in the future.
Does it mean, that TensorFlow/TensorFlow is just going to reference keras-team/keras in the future? And all development for tf.keras is going to happen directly at keras-team/keras?
Or do you still see copybara and internal review as a proxy?
Why was Keras merged into TF though?
Can tf.keras play nice with Swift For Tensorflow?
Good to know! Will that change the contribution policy in any way?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
