3 ms·
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 c
by DannyBee 9y ago
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)
- dikaiosune 9y agoparent's HN bio: > I run all the production and cloud programming language teams at Google, and am also an open source lawyer.
- DannyBee 9y agoThose 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 :)
- username223 9y ago> 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.
- cridenour 9y ago...what?
- username223 9y ago...who?
- bobajeff 9y agoThis still leaves open speculation for why Google developers are working on Swift.
- schwarrrtz 9y agoBecause Google devs write iOS apps, presumably in Swift, and want to contribute to the development of the language they use? Seems like the simplest explanation to me.
- trustfundbaby 9y ago... because they also write ios apps?
- DannyBee 9y agoI guess that's true, so i'll be explicit about that too: These Google developers are working on Swift because they are part of a team that supports internal-facing IOS tooling. (there really is nothing down this rabbit hole, FWIW)
- bobajeff 9y agoOh, that's way less exciting than what I was thinking. Thank you Mr. Bee for that bubble burst.
- DannyBee 9y agoOne thing to realize, if you don't already, is that we have come to accept that everyone notices everything we do on github at this point (and further, we assume that people look to see what googlers are doing outside the google org as well, and that pretty much everything placed on github will leak, and ...) If we were trying to keep something major under wraps, this would be an exceptionally bad way of achieving that. The public docs we have even show that we discourage private github repos for various reasons. Our general internal answer would be "don't stage it on github at all unless you are willing to see it leak"
- AndrewDavidson 9y agoThanks for response. Just curious - seems you saw this and replied in about 20 minutes of the post. Impressive speed. I know about google alerts etc and hacker news is popular, but curious how exactly you found this post so quickly? Someone saw it and pinged you or some automatic way?
- DannyBee 9y agoPeople have a tendency to ping me either about languages or open source stuff, especially when it seems a bit off the rails. So basically either legal problems or go generics. It's a fun life.
- AndrewDavidson 9y agoThanks for the reply - having a good network definitely helps in these situations. Thanks for the openness and honesty