I don't know much about Swift. Has anyone written in it something they can demo? Can it write gui and web apps? What's the biggest problem it solves and how do you like the language?
Google forked Swift
31–40 of 78 posts
Re: Google forked Swift
#32Can we change the title to “google forked the swift GitHub repo” or somesuch? The current one is rather misleading!
Re: Google forked Swift
#33Earlier quoted context omitted.
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 :)
> 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…
...what?
Re: Google forked Swift
#34Should change the title to "Google has a fork of Swift"
Re: Google forked Swift
#35how is this news ... hey look software was forked on github today!
Re: Google forked Swift
#36Earlier quoted context omitted.
That would be great news. Unification of mobile programming language.
That would be great for developers like you and me -- after all, our skills are most valuable when they are portable. How much more can we get done if we don't have to support multiple platforms? 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.
I understand the theory, but in practice this means if you want to implement a competing platform... you just need to write a Swift target!
Much easier for developers to go check out your platform.
More unification would likely also mean better abstraction layers across platforms, meaning that competing platforms could rely on those abstraction layers.
Think about how nice it is that most devices out there are running at least a flavor of Unix. You have a base-level expectation of how things can be integrated. There are of course differences, but generally if you write your stuff in a certain way you can use it almost everywhere!
And for those who don't want to work on Unix, all you need is a compatability layer to bring over some useful tools. Just get that C compiler up and running and you get a lot of stuff too!
The reason this is different from other forms of platform lock-in is that ultimately things like programming languages don't cover the full stack, so there are "obvious" places where you can swap either your language, the stuff underneath, or the stuff above it.
Re: Google forked Swift
#37Hi! 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! :)
Thank God. Otherwise this seemed like a very Microsoft/Java strategy.
I also worried having two different languages -- Google Swift and Apple Swift.
Re: Google forked Swift
#38Earlier quoted context omitted.
> 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…
...what?
...who?
Re: Google forked Swift
#39This 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.
I 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)
Re: Google forked Swift
#40Hi! 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! :)
Thank God. Otherwise this seemed like a very Microsoft/Java strategy.
[deleted]