51–60 of 235 posts
Hilarious that IBM still thinks of the enterprise as the arbiter of quality. Consumer is now setting the defacto standards, including on things like information security. IBM's days of having a voice in that conversation are probably more limited than they realize.
Earlier quoted context omitted.
1. Inferred static nominal typing with generics 2. 1st class support for Optionals 3. Support for Structs and Classes 4. Native binary & scripting mode 5. Automatic reference counting (instead of garbage collection) 6. Large standard library 7. Large corporate backer (Apple) 8. Open source 9. Good C, C++, & Obj-C interoperability 10. Decently fast ( https://medium.com/@qutheory/server-side-swift-vs-the-other-... )
Non C++ interop yet
Earlier quoted context omitted.
It's a systems language, and imo way more beautiful than c++.
Yeah but it can't replace C++. Swift was designed to make programming fun/nice not to replace C or C++.
When I recently interviewed at Apple I was told my position would primarily be coding in Java, but the team would be open to other languages as the project progressed and needs changed. I asked if they would consider Swift. Then was told that Swift wasn't production ready in their eyes. (I didn't get the job) I guess every team is different, but this attitude to dog fooding isn't great.
Apple isn't telling people to go use Swift on the server, IBM is. Apple is telling people to write iOS apps in Swift, which they are also doing themselves.
So... what's the "elevator pitch" for Swift? It has anything interesting over Elixir or Go (well, go's feature is "lack of feature" but you know what I mean) or Scala or Kotlin? I know that iOS and MacOS desperately needed a modern language, and great for them that they have it now, but does the rest of the world need it?
Earlier quoted context omitted.
I'm wondering what makes swift ready for the enterprise ecosystem. It barely seems to meet the requirements of the "enthusiastic consumer" outside of Apple OS.
To be ready for the enterprise ecosystem basically means that you can sue someone if things go wrong, and you can buy support packages for enormous sums of money. IBM is saying that you can 1) buy bluemix swift from them, and 2) sue them if anything goes wrong - but since they have a great legal team, they probably got ironclad agreements ready to go.
Cool! https://www.theguardian.com/australia-news/2016/sep/23/austr...
When I recently interviewed at Apple I was told my position would primarily be coding in Java, but the team would be open to other languages as the project progressed and needs changed. I asked if they would consider Swift. Then was told that Swift wasn't production ready in their eyes. (I didn't get the job) I guess every team is different, but this attitude to dog fooding isn't great.
> this attitude to dog fooding isn't great. Apple isn't telling people to go use Swift on the server, IBM is. Apple is telling people to write iOS apps in Swift, which they are also doing themselves.
I'm aware. This is the (humorous) point I'm attempting to make. IBM is adopting technologies faster then Apple. While Apple started it's life out as the Anti-IBM. Indeed it is still fulfilling this role. The (humorous) point being, their roles have in a way swapped.
So... what's the "elevator pitch" for Swift? It has anything interesting over Elixir or Go (well, go's feature is "lack of feature" but you know what I mean) or Scala or Kotlin? I know that iOS and MacOS desperately needed a modern language, and great for them that they have it now, but does the rest of the world need it?
Features don't matter much I'm afraid.