_31

Very interesting data. Are you planning on making it available via an API?

Great read!

I'm going to steal that use of 'typealias' when defining a closure that uses @escaping. Those method definitions are always so messy looking, this really cleans it up.

I haven't had the exact issue discussed in the article, but I have noticed that they have been really aggressive with rejections lately. Just this last week an app I'm trying to get into the store has been rejected 4 times, with the same exact automated message. I respond with an assertion of my apps compliance, but get the same automated response. These are the first rejections I've received in 7 years of submitting apps.

+1 for Siraj Raval's YouTube channel. Videos are quick, entertaining and give a good overview of a lot of ai/ml concepts. Some of the content is a little over the top (i.e. memes & breaking out into song), but overall really well put together.

That's true Google never named Kotlin as a replacement to Java. Although naming it a first-class Android language seems like a pretty big move (actions over words), and given an official option between Java and Kotlin I believe most dev's will begin moving towards Kotlin. intended was probably the wrong word for me to use, should have been probable or likely.

Past the syntax similarities, both of these languages are intended replacements for an 'old' language (Objective-C => Swift, Java => Kotlin) on a dominant mobile platform, with interoperability as a major selling point (requirement?). As a mobile dev (mainly iOS) this is awesome to see and although I love me some Objective-C, working with swift has been a pleasure. Now Java on the other hand... (shudders). With Google making Kotlin an official/first-class language and the syntax being so similar to swift I could see myself spending more time working with Android.