This API style was initially introduced by Chainer in 2015, and in 2017 multiple other frameworks adopted it (including those listed above). In the context of Keras, I call it "the Model subclassing API". It's a good fit for NLP research in particular!
-
-
Show this thread
-
You'll hear some say, "you can't implement X in framework Y, you need framework Z". It was already nonsense before all frameworks supported the same API style, but it's even more ridiculous now that you can port code from one library to any other with only minor syntax changes
Show this thread -
It's in the same category of nonsense as people claiming "you get better accuracy if you implement this model in framework X!" -- the output of an algorithm does not depend on the language you implement it in.
Show this thread
End of conversation
New conversation -
-
-
The lower left version (PyTorch I think) overwrites the first layer in the constuctor, so not quite the same
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
MXNet, Keras, pytorch, chainer? Left -> right
- End of conversation
New conversation -
-
-
I'm just a beginner so going to assume from "Block" - "Gluon" "Model" - "keras (tf backend)" "Module" - "torch" "Chain" - "Chainer"??
- End of conversation
New conversation -
-
-
I love this. It's like
@EdwardTufte's small multiples, but with code.
-
And with a typo :p
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
