Earlier quoted context omitted.
What are you looking for in deployment friendliness? There's TorchScript to run your code faster (which is a work in progress)
One of the major benefits of TF 2.0 is apparently the capability to quickly deploy to TPU units with a single parameter change. (I haven't tried it, just followed the marketing). AFAIK, This is still being worked on PyTorch via XLA, but not quite there yet.
Tensorflow 2.0 Beta 0
31–40 of 44 posts
Re: Tensorflow 2.0 Beta 0
#32Earlier quoted context omitted.
From what I understand this is mostly because they hired the Swift guy. I understand the benefits compared to Python (although I would have preferred Go or Kotlin). But what happens when the guy eventually moves on in a year or two?
Google's making a big investment in Swift, so if Chris left and they were interested in continuing to support it they shouldn't have a problem. I've gone to Swift on the Server conferences hosted/sponsored by Google, their (non-TF) Swift teams are building some cool Swift tools, etc.
Swift is not properly supported on linux, which is Google's main platforms.
Re: Tensorflow 2.0 Beta 0
#33Earlier quoted context omitted.
Google's making a big investment in Swift, so if Chris left and they were interested in continuing to support it they shouldn't have a problem. I've gone to Swift on the Server conferences hosted/sponsored by Google, their (non-TF) Swift teams are building some cool Swift tools, etc.
Google is a Go shop, specially when it comes to servers. Swift is not properly supported on linux, which is Google's main platforms.
Re: Tensorflow 2.0 Beta 0
#34Earlier quoted context omitted.
Google's making a big investment in Swift, so if Chris left and they were interested in continuing to support it they shouldn't have a problem. I've gone to Swift on the Server conferences hosted/sponsored by Google, their (non-TF) Swift teams are building some cool Swift tools, etc.
Google is a Go shop, specially when it comes to servers. Swift is not properly supported on linux, which is Google's main platforms.
Re: Tensorflow 2.0 Beta 0
#35Earlier quoted context omitted.
Google is a Go shop, specially when it comes to servers. Swift is not properly supported on linux, which is Google's main platforms.
Google is not at all a Go shop. Google is a C++ shop, especially when it comes to servers.
Google has been gradually moving away from C++ and Java since 2012. See this quora post with multiple references from Google employees.
https://www.quora.com/How-is-Go-used-at-Google-What-could-be...
Re: Tensorflow 2.0 Beta 0
#36Earlier quoted context omitted.
Google is a Go shop, specially when it comes to servers. Swift is not properly supported on linux, which is Google's main platforms.
This is incorrect; swift is open source and has linux deployments : https://swift.org/download/
Re: Tensorflow 2.0 Beta 0
#37Earlier quoted context omitted.
Google's making a big investment in Swift, so if Chris left and they were interested in continuing to support it they shouldn't have a problem. I've gone to Swift on the Server conferences hosted/sponsored by Google, their (non-TF) Swift teams are building some cool Swift tools, etc.
Google is a Go shop, specially when it comes to servers. Swift is not properly supported on linux, which is Google's main platforms.
You will even notice that it is seldom supported when they announce new server products SDKs.
Re: Tensorflow 2.0 Beta 0
#38Earlier quoted context omitted.
Google is not at all a Go shop. Google is a C++ shop, especially when it comes to servers.
(that contradicts your earlier comment) Google has been gradually moving away from C++ and Java since 2012. See this quora post with multiple references from Google employees. https://www.quora.com/How-is-Go-used-at-Google-What-could-be...
Go is mostly a Docker/Kubernetes thing.
Re: Tensorflow 2.0 Beta 0
#39Earlier quoted context omitted.
Maybe I'm not up to speed with the latest PyTorch, but to me Keras feels much more natural. In Keras if you want to define a deep learning network, then you just do that, you specify the first layer, the second layer, etc, then you calibrate over some test and validation samples, using a certain flavor of gradient descent, for a given loss function. In PyTorch, you have to define a class, with a constructor, some met…
in Keras I can't (easily) change the architecture of a learner after I defined it I'm not sure what you mean here, because only PT lets you change architecture after you define it, while TF/Keras uses a static precompiled graph. Now that's changing with eager mode, but that used to be the main advantage of PT.
Re: Tensorflow 2.0 Beta 0
#40Any news on Swift for Tensorflow? I’m skeptical of how much practical benefit it will provide but still willing to take a look at it. There doesn’t seem to be any mention of it here.