Re:Keras 3.0
by eigenvalue on Tuesday November 28, 2023 @10:38AM
(#38446826)
Seems like they missed the boat and the whole world has moved on. Maybe if this came out 2 years ago it would be more relevant.
[ Parent
| on HN ]
What is relevant now?
Re:Keras 3.0
by elforce002 on Tuesday November 28, 2023 @11:47AM
(#38447765)
I use keras for CV but for DL at work, we started moving towards pytorch and closely following modular.
PyTorch has the nicest debugging experience. JAX is supposed to be powerful too, but I'm skeptical of its static graph which is what made TensorFlow such a chore. I'm whishful about Mojo, in theory it sounds great.
On the contrary, that's why I find Keras 3 interesting (although I don't see myself switching anytime soon). It supports both PyTorch and JAX, and Keras Core models/layers can be used interchangeably with PyTorch modules: https://twitter.com/fchollet/status/1697020631752298982
[dead]
I've only experienced him polite and responsive. That said, maintaining Keras must have been an unhealthy amount of work for one person, and I think OSS developers in that situation deserve the benefit of doubt that being brusque or ignoring issues is not a character flaw, but a defense mechanism to keep their sanity.
Re:Keras 3.0
by AlecSchueler on Tuesday November 28, 2023 @11:00AM
(#38447135)
Why do you say that?
Re:Keras 3.0
by _Wintermute on Tuesday November 28, 2023 @11:16AM
(#38447341)
I remember one instance of someone posting a legitimate and well-written github issue about argument unpacking in keras. Instead of addressing or responding to the issue, the Keras creator decided to publicly rant about the person on twitter, for seemingly no reason whatsoever.