3 ms·
The part about bad Keras<->Tensorflow.js interop is classic Tensorflow. Using TF always felt like using a bunch of vaguely related tools put under the same umbr
by cherryteastain 2y ago
The part about bad Keras<->Tensorflow.js interop is classic Tensorflow. Using TF always felt like using a bunch of vaguely related tools put under the same umbrella rather than an integrated, streamlined product.
Actually, I'll extend that to saying every open source Google library/tool feels like that.
- Retr0id 2y agosomething something Conway's law
- alecco 2y agorelated (15 days ago) https://news.ycombinator.com/item?id=42130881 https://news.ycombinator.com/item?id=42130881 on Francois Chollet is leaving Google > "Why did you decide to merge Keras into TensorFlow in 2019": I didn't! The decision was made in 2018 by the TF leads -- I was a L5 IC at the time and that was an L8 decision.