5 ms·
That's good to hear, but S4TF has failed to gain any real traction among ML users and was started over two years ago. I've heard not many care about it apart fr
by amznthrowaway5 7y ago
That's good to hear, but S4TF has failed to gain any real traction among ML users and was started over two years ago. I've heard not many care about it apart from the core team and now that Lattner is gone it's likely Google will send it to the graveyard soon.
- byt143 7y agohttps://twitter.com/clattner_llvm/status/1222032740897284097 https://twitter.com/clattner_llvm/status/1222032740897284097 Jeff Dean seems to disagree. Also, I think it hasn't picked up steam because it just isn't mature enough yet
- nl 7y agoThat's a very non-committed response from Jeff Dean! I suspect it will drift along like the Java TensorFlow wrapper. Useful in some specific circumstances, but unused outside that.
- byt143 7y agohttps://forums.fast.ai/t/swift-for-tensorflow/40167/72 https://forums.fast.ai/t/swift-for-tensorflow/40167/72
- nl 7y agoI think Lattner saying that just confirms there are concerns. The only people who seem to be saying it will continue are people outside Google. Crucially there's no one within Google saying they use it for internal projects.
- xvilka 7y agoAnd it's a good news - Swift is a niche, vendor-locked language. Using something like Rust for production level and something like Julia for R&D stage is a better fit.