21–30 of 78 posts
This is being used as a staging place for putting patches so they can be turned into pull requests, nothing more. Sorry to bust any conspiracy theories. (You can see this happens on >100 of the swift forks :P)
parent's HN bio: > I run all the production and cloud programming language teams at Google, and am also an open source lawyer.
Perhaps this is the start of moving Android Apps to Swift. Which, per rumor was considered last year: "About the time Swift was going open source, representatives for three major brands — Google, Facebook and Uber — were at a meeting in London discussing the new language. Sources tell The Next Web that Google is considering making Swift a “first class” language for Android" https://thenextweb.com/dd/2016/04/07/google…
That would be great news. Unification of mobile programming language.
However, the interests of vendors are diametrically opposed to our interests as developers -- it is all about vendor lockin, and making it as hard as possible for us to support competing platforms.
Google corporate policy, to the best of my knowledge (I do not and have never worked for Google but I asked lots of questions when evaluating an offer), is that it's significantly easier to let Google retain copyright on your open source work, and if it's on GitHub you have to host your repo at github.com/google if Google retains copyright. ("Forks" with no code changes ending up at the top of HN, as if they signaled…
They are now a bit out of date, a few things have been simplified/relaxed (generally, the goal is as little process as possible).
Then again, people also like to super-duper parse the words in the docs, which are not really written to be parsed that way.
This is being used as a staging place for putting patches so they can be turned into pull requests, nothing more. Sorry to bust any conspiracy theories. (You can see this happens on >100 of the swift forks :P)
Earlier quoted context omitted.
parent's HN bio: > I run all the production and cloud programming language teams at Google, and am also an open source lawyer.
Those words are pretty literal, actually. Which means I don't own Swift at Google, i just know what they are doing because i approved it another capacity :)
Are you sure you didn't mean ";)" there?
> I run all the production and cloud programming language teams at Google, and am also an open source lawyer.
Smiley-face to you as well, friend. You get paid well into six figures to do this, while I just try to figure out how you're screwing me on evenings and weekends. I don't pretend to understand the technicalities of what you're typing, but I suspect that I will lose.
This is being used as a staging place for putting patches so they can be turned into pull requests, nothing more. Sorry to bust any conspiracy theories. (You can see this happens on >100 of the swift forks :P)
This still leaves open speculation for why Google developers are working on Swift.
Seems like the simplest explanation to me.
This is being used as a staging place for putting patches so they can be turned into pull requests, nothing more. Sorry to bust any conspiracy theories. (You can see this happens on >100 of the swift forks :P)
This still leaves open speculation for why Google developers are working on Swift.
Hi! I’m one of the engineers on this. We’ve got some work we’re collaborating on - all of which is going upstream - and we wanted a shared place to stage it while we prepare PRs. I’ll be pushing a statement to our fork tomorrow. (I’m personally working on Bazel rules and contributions to lib/Syntax. If you find that exciting, please get in touch! :)