4 ms·

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.

• ipunchghosts 3y ago
  [flagged]
  • AlecSchueler 3y ago
    Why do you say that?
    • _Wintermute 3y ago
      [flagged]
      • kerasteam 3y ago
        Yeah, that never happened. We process dozens of bug reports and feature requests every week, and we listen to them.
        • _Wintermute 3y ago
          [flagged]
  • wewxjfq 3y ago
    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.
• pennaMan 3y ago
  What is relevant now?
  • arketyp 3y ago
    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.
    • techwizrd 3y ago
      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 https://twitter.com/fchollet/status/1697020631752298982
  • elforce002 3y ago
    I use keras for CV but for DL at work, we started moving towards pytorch and closely following modular.
• deleted 3y ago
  [deleted]