5 ms·
The blog post links to a tweet and that tweet has a couple more details. The new keras is going be tensorflow-only and build on top of tf.contrib.layers (so a c
by ma2rten 10y ago
The blog post links to a tweet and that tweet has a couple more details. The new keras is going be tensorflow-only and build on top of tf.contrib.layers (so a complete rewrite).
https://twitter.com/fchollet/status/820746845068505088 https://twitter.com/fchollet/status/820746845068505088
- mgreg 10y agoIt actually sounds like Keras as we know it will continue to exist and support both Theano and TF. Theano support will continue for as long as Keras exists. This integration changes nothing for existing Keras users, only for TF users. - https://twitter.com/fchollet/status/821090410659344384 https://twitter.com/fchollet/status/821090410659344384 Rather than a "new" Keras it sounds (I could be wrong) as if the Keras API will be included now with TF as an alternative way of interacting with TF (as it has been for some time) and simple bundled with TF.
- attractivechaos 10y agoI wonder how Keras will be integrated into TF and how keras-in-tf will evolve with the separate Keras. More specifically, how many more APIs will keras-in-tf have in addition to the current keras? Wouldn't this hurt keras as a backend-agnostic library? Will the keras-in-tf APIs always keep in sync with standalone-keras? I will be curious to see how these pan out before getting too excited.
- nl 10y agoThat isn't what that Tweet says at all. Notability he makes this very explicit: Theano support will continue for as long as Keras exists. This integration changes nothing for existing Keras users, only for TF users. https://mobile.twitter.com/fchollet/status/821090410659344384 https://mobile.twitter.com/fchollet/status/82109041065934438...