An article I wrote started a conversation about Swift for Android

And believe it or not, that’s all I wanted it to do.

Recently, I wrote an article about the potential that Google would make Swift a ‘first class’ language for Android. Some loved hearing the news, others were angry I said anything at all.

Here’s why I wrote it.

I first heard about Google, Facebook and Uber entertaining the thought of using more Swift a few weeks ago. It was mentioned to me privately at a meeting while I was in San Francisco; an off-hand comment that sparked my interest.

First, I confirmed that I was okay to even discuss what was mentioned in that chat. The person who told me is someone I value as a friend and colleague, and though I’m charged with finding these sort of things to write about so the website gets those precious, precious clicks — I’m not going to ruin relationships just to get some views on a webpage. That’s not me.

In following up, I went to some others who maybe in the know about Swift for Android (because that was the more interesting Swift-y topic in my view). The reaction was either ‘how did you know about that?’ or ‘I’ve heard it, but I can’t see it happening anytime soon.’ Oddly, nobody was denying the value of Swift for Android or suggesting it wasn’t something that should happen (at least someday).

Touching on developer issues can be sensitive, especially when you’r talking languages. There are some people who’ve spent an eternity in Java, and the mere suggestion it was being challenged incensed a few of them. I respect that.

I think part of the outrage is Swift was born at Apple, so the old guard might think using it for Android means Apple is officialy better than Google; iOS a better mobile platform than Android. Nothing could be further from the truth in 2016. Swift is open source, and I’ve been pleasantly surprised by just how wonderfully Apple is embracing that. The platform wars are over and no, it hasn’t spread to languages.

On the other hand, Swift developers seem to be welcoming the opportunity to write for Android. They like the idea of their favorite language being useful in more places. I respect that, too.

Full stop: yes, I’m a Swift developer when I’m not writing, but I’m also of the opinion that full-on ‘replacing’ Java is not something Google would (or should) ever do. If anything, I think they’d support Swift and let it coexist with Java — and if the Android developer world tilts on its axis and Swift organically replaces Java someday, Google would adjust accordingly.

I’ve been sitting in the middle of all that opinion, suffering the vitriol and experiencing the praise. That attention comes with the territory, but what brings me the most joy is that it sparked a conversation about Swift for Android.

Even if they hate the idea, people are talking about it. That was the real goal; I didn’t set out to position Swift as a Java usurper, or that Google should make a move to Swift any time soon.

Instead, I wanted people to consider Swift for Android. If you hate the idea, please don’t direct energy at being mad about it. Instead, do the dilligence to make sure Java remains at the top of the Android heap by contributing to your community.

Swift developers interested in Android should do the same. Work at getting Swift functional for Android. It’s only then that we know if it’s a good idea or not.

Side note: For those who like to ask ‘what about Go or Dart?’, two things: one, both were basically laughed at when I brought it up to our sources (neither is as developed as Swift, nor does it seem as though progress is quick enough for either to win anyone over yet)— two, those developers should also be working to make sure the languages don’t get lost in the shuffle.

In times like these, I wish I could divulge a few of our sources because it would change the narrative quite a bit. But there’s also beauty in sparking a conversation that’s organic, and gets people thinking critically (just please remember that there’s a diference between critical and asshole when sharing your opinions online).

It was my aim in writing the article, and I consider it a success, clicks be damned.