Great news! Coding in Swift is fantastic and I would love to see it coming to more platforms, maybe even on servers. It could become a serious Javascript competitor due to its elegant syntax, the type safety and speed.
Swift is Open Source
91–100 of 458 posts
Re: Swift is Open Source
#92Now that swift is opensource i'm looking forward to some better tools being released for it. Right now xcodes support of swift is pretty lacking. No refactoring, and compile errors are fairly ambiguous sometimes.
Since this has linux support i wonder if xcode or something similar will be ported to linux.
Re: Swift is Open Source
#93The Swift port for Linux seems to only support x86-64 for now. https://swift.org/blog/swift-linux-port/ I would like to see how swift could run on Linux ARM devices (Raspberry Pi 2/Beagleboard/etc) and other platforms; given that the runtime is already on iOS devices. Kudos to Apple for open-sourcing Swift.
Try to compile it and see if you can get it to work?
Re: Swift is Open Source
#94Earlier quoted context omitted.
Oops. I did try to check his site, but it was coming up blank for me.
Your theory might still stand. He may know people at Apple, so this does not completely discard the scenario.
He may have heard it direct from Apple. They have a close partnership for developing enterprise iOS apps, and have been for almost two years.
I had no idea myself until I went to interview at IBM. I haven't had the opportunity to work with Swift professionally though, so they went with someone else. Possibly the OP :P
https://www.apple.com/pr/library/2014/07/15Apple-and-IBM-For...
Re: Swift is Open Source
#95I wonder if Apple is positionning it as a competitor to Google's Go? They are hinting at a usage beyond just iOS and OS X.
I'm much more thrilled about Swift the about Go. Sure Go has a head start in server-side department, but from what I know of Swift I'd much rather write webapps in it then in Go.
Many webapps have a kind of "highlevelness" to them, and Swift nicely addresses that with it's features. Go is somehow on a kind of feature diet that's just not my cup of tea. And in terms of low-high-level-ness it I put it somewhere in between Swift and the obviously low-level Rust.
Re: Swift is Open Source
#96Testing the binaries on ubuntu decompressed to to $HOME/swift and trying to execute swift: Welcome to Swift version 2.2-dev (LLVM 46be9ff861, Clang 4deb154edc, Swift 778f82939c). Type :help for assistance. 1> help opening import file for module 'SwiftShims': No such file or directory 1> I could not find any mention to environment variables that could be used to override default locations, like SWIFT_LIBRARY_PATH or s…
Run Systrace on it and you'll see what it is looking for.
I used ltrace and saw a call to getenv("SDKROOT") but pointing it to any of:
export SDKROOT=$HOME/swift/usr
or
export SDKROOT=$HOME/swift/usr/lib
or
export SDKROOT=$HOME/swift/usr/lib/swift
All the above do not work, maybe when github is up we can see how to do it.
Re: Swift is Open Source
#97Not loading for me. Anyone experiencing the same issue?
Re: Swift is Open Source
#98Apache 2.0 License + Runtime Library Exception + copyright owned by the contributor (i.e. no assignment or CLA) + good community structure and documentation + code of conduct... well done, Apple!
Anybody knows what effects of the "copyright owned by the contributor" are in the context of Swift's Apache license?
I guess the "good side" is that the lawyers of other companies probably like when the code made by their programmers keeps being copyrighted by the company. But it is still an Apache license, so they can't demand too much from the users of the code.
Still, are there any negative aspects? Any imaginable danger?
Can the standard library have problems with (once in the future) having different copyright holders for its different parts?
Re: Swift is Open Source
#99https://github.com/apple/ This organization has no public repositories.
[deleted]
Re: Swift is Open Source
#100Linux support is hinted at in examples: #if os(Linux) import Glibc #else import Darwin.C #endif https://swift.org/package-manager/#example-usage
I guess the idea is that you will be able to run the same code from your fronted (iOS, OS X) also in the backend (some Linux server).