10 ms·

Github repo is live now. https://github.com/apple/swift https://github.com/apple/swift First ever commit found here https://github.com/apple/swift/commit/afc81

by nikon 11y ago

Github repo is live now. https://github.com/apple/swift https://github.com/apple/swift First ever commit found here https://github.com/apple/swift/commit/afc81c1855bf711315b8e5de02db138d3d487eeb https://github.com/apple/swift/commit/afc81c1855bf711315b8e5...

thecodemonkey 11y ago
It's really interesting that they decided to retain the full history! It also gives away some information about the initial contributors and the timeframe of when they started.
- joeflow 11y ago
  I love it. I've never taken a compiler class so going through and reading all the commits since day one is really fascinating. It's easy to see exactly how the language and structure of the code base came to be. Super cool in my book.
  - dafrankenstein2 11y ago
    right!
- elwell 11y ago
  https://github.com/apple/swift/commit/afc81c1855bf711315b8e5de02db138d3d487eeb#commitcomment-14769143 https://github.com/apple/swift/commit/afc81c1855bf711315b8e5...
- sdesol 11y ago
  Here are some visual aids that better shows how this project has evolved. It also shows how active things are today. http://imgur.com/a/HyQWv http://imgur.com/a/HyQWv
  - j_s 11y ago
    Anyone willing to make a Gource video? https://github.com/acaudwell/Gource/wiki/Videos https://github.com/acaudwell/Gource/wiki/Videos
keehun 11y ago
It's cool to see that it was basically all Lattner at the beginning and his decisions about the license/exception still stand. EDIT: License/Header in each of files were apparently retroactively added.
- TazeTSchnitzel 11y ago
  Look carefully at that copyright date: 2014-2015. They've rewritten history.
  - Uzomidy 11y ago
    It looks like they used an automated tool to add copyright notices to files in the repository. Probably were required to do that by legal. So it's not 100% faithful history, but close.
    - rcthompson 11y ago
      This raises some interesting legal questions. If I start a git repo and only add a license in the Nth commit, does that license apply retroactively to a checkout of the first N-1 commits? What if I start out with one license but I change it in the Nth commit? If someone clones the git repo with the Nth commit in it and then checks out an earlier commit, which license applies? (For simplicity, assume I am the only author of the repo, so I can always change the license arbitrarily whenever I want to.)
      - scolson 11y ago
        You can retroactively make a license more open, but you cannot retroactively make it more closed.
        tzs 11y ago
        That may be true for some open source/free software licenses, but I don't think it is true for all. It would depend on whether or not the license says it is irrevocable and whether or not the license is sub-licensable. Let's suppose Alice gives Bob a copy of code whose copyright is owned by Charles, and the code was licensed to Alice under and open/free license. If the license is revocable, Charles should be able to revoke the licenses for existing copies, and offer replacements that are more closed. Those who do not accept that replacement license should, I think, be able to continue using the copies they have but they will not have a license. Their rights will be limited to those rights that copyright law gives to owners of legally made copies. For software, that would mean they could use the code, but could not make and distribute copies or derivative works. If the license is irrevocable, then Charles should not be able to take away existing licenses, but he may be able to stop issuing new licenses. That brings is to the issue of sub-licensing. If the license is sub-licensable, then when Alice gives Bob a copy, Alice can also give Bob a license via her sub-licensing right. If the license is not sub-licensable, then Alice cannot give Bob a license. Bob's license has to come from Charles. So what happens if before Alice gives Bob a copy, Charles has decided to stop issuing new licenses? I think Alice should still be able to distribute to Bob, because she has a license that allows distribution. Without a license from Charles, though, Bob would only be able to use the code for things copyright allows the owner of a particular legal copy to do without a license, which would be use it himself but would not include making and distributing copies and derivative works. Alice might be able to argue that the terms of her license with Charles require Charles to provide licenses to those whom Alice distributes to, and so perhaps Alice could go to court to force Charles to keep granting licenses. I don't recall enough from law school about third party beneficiaries to figure out whether Bob could sue Charles based on Alice's license to get a license from Bob for a copy he got from Alice, or whether, if Charles sued Bob for copyright infringement Bob could use Charles' contractual obligation to Alice in his defense.
prateekbhatt 11y ago
They just made public the repo with the guidelines for Swift's evolution process: https://github.com/apple/swift-evolution/blob/master/process.md https://github.com/apple/swift-evolution/blob/master/process...
mingodad 11y ago
Interesting there is no link to add issues to those repositories !
- weaksauce 11y ago
  Probably because they will want to use radar for bugs and general discussion might be done like Linux mailing lists. Edit yeah. that's basically how they are handling it but with the exception that they are using a public jira instance for language bugs, radar for xcode and nda bound bugs and a mailing list for general discussion.
  - kennywinker 11y ago
    https://bugs.swift.org/ https://bugs.swift.org/ <-- public jira instance
deleted 11y ago
[deleted]
pippy 11y ago
Lexer.cpp: int X; Interesting that they started with git, instead of even a very small section of working code first
- cooper12 11y ago
  I think it's because they need a repo before they can start collaborating, so it's best to set it up ASAP to allow people to start pushing code. In my opinion it also helps to set up the initial repo right away so you can benefit from version control features and be in the mindset of making proper commits instead of a huge initial commit that appears out of thin air.
dom96 11y ago
It's also interesting to see the graph of contributors (https://github.com/apple/swift/graphs/contributors https://github.com/apple/swift/graphs/contributors). I noticed for example that Slava Pestov (The creator of the Factor programming language) has made a number of commits. Apple has hired some really smart people to work on Swift! Edit: Also jckarter the creator of the Clay programming language is in there too!

by nikon 11y ago

thecodemonkey 11y ago

It's really interesting that they decided to retain the full history! It also gives away some information about the initial contributors and the timeframe of when they started.

joeflow 11y ago
I love it. I've never taken a compiler class so going through and reading all the commits since day one is really fascinating. It's easy to see exactly how the language and structure of the code base came to be. Super cool in my book.
- dafrankenstein2 11y ago
  right!
elwell 11y ago
https://github.com/apple/swift/commit/afc81c1855bf711315b8e5de02db138d3d487eeb#commitcomment-14769143 https://github.com/apple/swift/commit/afc81c1855bf711315b8e5...
sdesol 11y ago
Here are some visual aids that better shows how this project has evolved. It also shows how active things are today. http://imgur.com/a/HyQWv http://imgur.com/a/HyQWv
- j_s 11y ago
  Anyone willing to make a Gource video? https://github.com/acaudwell/Gource/wiki/Videos https://github.com/acaudwell/Gource/wiki/Videos

keehun 11y ago

It's cool to see that it was basically all Lattner at the beginning and his decisions about the license/exception still stand. EDIT: License/Header in each of files were apparently retroactively added.

TazeTSchnitzel 11y ago
Look carefully at that copyright date: 2014-2015. They've rewritten history.
- Uzomidy 11y ago
  It looks like they used an automated tool to add copyright notices to files in the repository. Probably were required to do that by legal. So it's not 100% faithful history, but close.
  - rcthompson 11y ago
    This raises some interesting legal questions. If I start a git repo and only add a license in the Nth commit, does that license apply retroactively to a checkout of the first N-1 commits? What if I start out with one license but I change it in the Nth commit? If someone clones the git repo with the Nth commit in it and then checks out an earlier commit, which license applies? (For simplicity, assume I am the only author of the repo, so I can always change the license arbitrarily whenever I want to.)
    - scolson 11y ago
      You can retroactively make a license more open, but you cannot retroactively make it more closed.
      - tzs 11y ago
        That may be true for some open source/free software licenses, but I don't think it is true for all. It would depend on whether or not the license says it is irrevocable and whether or not the license is sub-licensable. Let's suppose Alice gives Bob a copy of code whose copyright is owned by Charles, and the code was licensed to Alice under and open/free license. If the license is revocable, Charles should be able to revoke the licenses for existing copies, and offer replacements that are more closed. Those who do not accept that replacement license should, I think, be able to continue using the copies they have but they will not have a license. Their rights will be limited to those rights that copyright law gives to owners of legally made copies. For software, that would mean they could use the code, but could not make and distribute copies or derivative works. If the license is irrevocable, then Charles should not be able to take away existing licenses, but he may be able to stop issuing new licenses. That brings is to the issue of sub-licensing. If the license is sub-licensable, then when Alice gives Bob a copy, Alice can also give Bob a license via her sub-licensing right. If the license is not sub-licensable, then Alice cannot give Bob a license. Bob's license has to come from Charles. So what happens if before Alice gives Bob a copy, Charles has decided to stop issuing new licenses? I think Alice should still be able to distribute to Bob, because she has a license that allows distribution. Without a license from Charles, though, Bob would only be able to use the code for things copyright allows the owner of a particular legal copy to do without a license, which would be use it himself but would not include making and distributing copies and derivative works. Alice might be able to argue that the terms of her license with Charles require Charles to provide licenses to those whom Alice distributes to, and so perhaps Alice could go to court to force Charles to keep granting licenses. I don't recall enough from law school about third party beneficiaries to figure out whether Bob could sue Charles based on Alice's license to get a license from Bob for a copy he got from Alice, or whether, if Charles sued Bob for copyright infringement Bob could use Charles' contractual obligation to Alice in his defense.

prateekbhatt 11y ago

They just made public the repo with the guidelines for Swift's evolution process: https://github.com/apple/swift-evolution/blob/master/process.md https://github.com/apple/swift-evolution/blob/master/process...

mingodad 11y ago

Interesting there is no link to add issues to those repositories !

weaksauce 11y ago
Probably because they will want to use radar for bugs and general discussion might be done like Linux mailing lists. Edit yeah. that's basically how they are handling it but with the exception that they are using a public jira instance for language bugs, radar for xcode and nda bound bugs and a mailing list for general discussion.
- kennywinker 11y ago
  https://bugs.swift.org/ https://bugs.swift.org/ <-- public jira instance

deleted 11y ago

[deleted]

pippy 11y ago

Lexer.cpp: int X; Interesting that they started with git, instead of even a very small section of working code first

cooper12 11y ago
I think it's because they need a repo before they can start collaborating, so it's best to set it up ASAP to allow people to start pushing code. In my opinion it also helps to set up the initial repo right away so you can benefit from version control features and be in the mindset of making proper commits instead of a huge initial commit that appears out of thin air.

dom96 11y ago

It's also interesting to see the graph of contributors (https://github.com/apple/swift/graphs/contributors https://github.com/apple/swift/graphs/contributors). I noticed for example that Slava Pestov (The creator of the Factor programming language) has made a number of commits. Apple has hired some really smart people to work on Swift! Edit: Also jckarter the creator of the Clay programming language is in there too!