271–280 of 458 posts
Earlier quoted context omitted.
there is no source code, yet.
Right now there is!: https://github.com/apple/swift Also, the dependencies to build swift looks fine to build it on other architectures. I'll try to build it for the Raspberry Pi 2 to see.
I haven't gotten it to build yet, maybe I should read the manual, but I'm a man, damnit, so I'll do that once I've tried absolutely everything else.
Earlier quoted context omitted.
Interesting there is no link to add issues to those repositories !
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.
The programming language eco system is really improving rapidly and efficiently. It seemed the developer's toolkit was limited by the languages created 20+ years ago but within the last few years we're seeing a renaissance in developer toolkits as well as development philosophies. Languages like Go, Rust, and now Swift are not only great from almost every aspect over the last generation languages like C, C++, Java, b…
"learning/mastering both Go and Swift is the best decision you can make" is a very bold claim. In my area we use Go for some systems but found it scales badly from an engineering point of view to larger more complicated systems, compared to languages like Java and Scala. The JVM has much more mature tooling and libraries too. For mobile applications it will be a while until Swift is stable on Android, so some of the…
Earlier quoted context omitted.
Not really. Your typical corporate IP lawyer might feel queasy about the collective copyright aspect, but so much of the open source world works this way now... they can suffer in their jocks. One important question they'll ask is: "Who can enforce the copyright and licence?" (Which is when the subtle difference between joint and collective copyright matters.) Non-trivial contributions are made under the terms of the…
> Your typical corporate IP lawyer might feel queasy about the collective copyright aspect, but so much of the open source world works this way now... they can suffer in their jocks. This is a bad attitude if you want buy-in from large organizations. If you're not worried about that, no problem, but if buy-in is your goal (and I'm sure it's Apple's goal here) you can't just tell potential contributors to "suffer in t…
Earlier quoted context omitted.
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.
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 aut…
No, unless you explicitly state it somewhere (and even then, I'm not certain).
If they add a license to the older commits via rewriting history then yes, those older commits will now be licensed. If they don't do so, then copyright will be default i.e. you can't do anything with it.
Now, if they had a large history and didn't retroactively license files, but just pushed the repository out all at once, I have no idea if the license on the latest commit would apply to the older commits. In the end, the question is all about whether or not Apple has the legal ability to sue you for copyright infringement.
What kind of trolling is that ? >I think we should use GPL v3 instead. https://github.com/apple/swift/pull/17
http://www.h4labs.com/dev/ios/swift.html
It can be viewed daily or weekly, if you're only interest in recent blogs:
http://www.h4labs.com/dev/ios/swift.html?date=0
http://www.h4labs.com/dev/ios/swift.html?week=0
Finally, all the data is on Github:
Earlier quoted context omitted.
Look carefully at that copyright date: 2014-2015. They've rewritten history.
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.
Fantastic news that Swift is now open-source, though it came about 4 hours too late for my GotoBerlin presentation on Swift 2 Under the Hood (on SpeakerDeck at https://speakerdeck.com/alblue/swift-2-under-the-hood-gotobe... if you're interested) I've also open-sourced the SIL Inspector that I demonstrated ( https://github.com/alblue/SILInspector ) and written up a post on InfoQ covering the important points of this r…
git clone git@github.com:apple/swift.git swift
but you can use:
git clone https://...../apple/.... swift
and the same for the remaining libraries.