Hacker News Reader

Comment by agentgt | Hacker News Reader

I would not be surprised if the percentage of Apple's code that is in Swift is more or less the same percentage of Google's code using Golang (with Golang having a slight advantage maturity wise). I'm sure Dart is even less. Of course this is just anecdotal from talking with a few people from Google so I'm probably off. That being said C++ has a huge advantage in that it keeps improving where as Objective C from my ignorant understanding has little plans of being improved (google has a large C++ codebase).

View on HN

I would not be surprised if the percentage of Apple's code that is in Swift is more or less the same percentage of Google's code using Golang (with Golang having a slight advantage maturity wise).

That could be true, but what it's being used for is perhaps more important than the percentage. Not to underestimate the importance of a calculator, but it is known that Google uses Go in:

- dl.google.com

- Kubernetes

- Youtube's MySQL scaling infrastructure (Vitess)

- Google's mobile data compression proxy (Flywheel)

Of course, Go's first stable release was in 2012, so Swift still has some time to catch up ;).

Google uses Kubernetes? I thought it was just inspired by Borg and a 20% project.

I was under the impression that they intend on moving everything over to Kubernetes, in massive multi-thousand-host clusters.

Granted, the last I heard they had trouble scaling it up to hundreds of hosts, but there it is.

They are offering it as a service on Google Cloud Platform.

That's not quite true – Apple has added quite a few improvements to ObjC over the past few years. Not sure if this has slowed down since the introduction of Swift, but I presume they will still keep coming for now, since (as this article postulates), Apples still mainly uses ObjC internally.

That's true, but arguably, the changes introduced into Objective-C (ARC, properties) were to support a future compatibility with Swift. The fact that it simplified Objective-C was probably a bonus.

Jetbrains seems to be dogfooding pretty good with kotlin.

I have to imagine JVM interop is substantially easier than the ABI route but I'm not an expert in that area (that is it substantially easier to call legacy code and probably port). I do like Kotlin though.

Reply on news.ycombinator.com