Swift is similiar to Python but lucky, Swift lets you have curly braces which makes pretty formatting easier. I am a messy coder and I like when I am done, I do the pretty format and it makes it look pretty and follows the conventions.
My name is Skip Wilson, and this is the original online Swift REPL.
You should check out my popular Swift tutorials., and my pro tutorials.
I could see Apple offering an online service that included all the Apple Swift APIs.
Thank you so much, I dedicated one of my Jetson boards specifically for Swift. I can't wait until either CodeEnvy or Cloud 9, cloud based IDE web apps start supporting Swift. I don't mind using a local IDE for now but when I start to do real projects I really want to do it in the cloud. I've found by making a lot of my projects available to the public I get a lot of assistance from others, which helps me learn faster and develop more applications. Besides, CodeEnvy has become one of the best IDE's I've used, local, cloud or otherwise. This is going to be a lot of fun, I just love playing with stuff like this. First thing I need to do is start writing some API's for CUDA as it has become really important to my projects, I am able to produce better, faster GPU excelerated applications using CUDA than with OpenCL at the moment as the amount of code, libraries, applications in which to plunder for choice code easily outnumbers OpenCL 100 to 1, again, at this moment, it's getting better all the time for Open CL
Anyway thank you for the link, would you be interested in helping me create a thread here in which it's sole purpose is to help us be the best darn Swift programmers possible.
My name is Skip Wilson, and this is the original online Swift REPL.
You should check out my popular Swift tutorials., and my pro tutorials.
I could see Apple offering an online service that included all the Apple Swift APIs.
Thank you so much, I dedicated one of my Jetson boards specifically for Swift. I can't wait until either CodeEnvy or Cloud 9, cloud based IDE web apps start supporting Swift. I don't mind using a local IDE for now but when I start to do real projects I really want to do it in the cloud. I've found by making a lot of my projects available to the public I get a lot of assistance from others, which helps me learn faster and develop more applications. Besides, CodeEnvy has become one of the best IDE's I've used, local, cloud or otherwise. This is going to be a lot of fun, I just love playing with stuff like this. First thing I need to do is start writing some API's for CUDA as it has become really important to my projects, I am able to produce better, faster GPU excelerated applications using CUDA than with OpenCL at the moment as the amount of code, libraries, applications in which to plunder for choice code easily outnumbers OpenCL 100 to 1, again, at this moment, it's getting better all the time for Open CL
Anyway thank you for the link, would you be interested in helping me create a thread here in which it's sole purpose is to help us be the best darn Swift programmers possible.
Love to join you and contribute any way I can ...
My stuff will be Apple-oriented, and hopefully, at a higher level than drivers or flogging 'Nix at the CLI level *
* I did a lot of that a few years back ... but I find as I've gotten older my brain has filled up -- every time I learn a new technology, my brain forgets one that I already know (knew). CoBOL, Pascal, RPG ... BASIC, Perl, Objective-C ... What are those?
Anyway let me know by PM or on an AI thread, here -- when I can help!
When I posted earlier on this thread that "this changes everything" -- little did I know that it also applied to Apple's Swift 2.0 syntax, structure and implementation :no:
None of my existing Swift apps even compile anymore ... Back to being a Swift Noob, with few places to seek assistance.
* I did a lot of that a few years back ... but I find as I've gotten older my brain has filled up -- every time I learn a new technology, my brain forgets one that I already know (knew). CoBOL, Pascal, RPG ... BASIC, Perl, Objective-C ... What are those?
None of my existing Swift apps even compile anymore ... Back to being a Swift Noob, with few places to seek assistance.
Well, I can include in my <old> language list: COBOL, C, C++, Pascal, RPG II, BASIC, Foxpro, 8086 Assembly, Objective-C, Java
And Scala, Swift on my new one.
The 1.2 to 2.0 code migration failed that badly????
I keep reading on several blogs/sites about the Google Go language so I'll be blunt: Outside of Google and a few FOSS stalwart fans of theirs no one within the LLVM Ecosystem could give a **** about Go.
My stuff will be Apple-oriented, and hopefully, at a higher level than drivers or flogging 'Nix at the CLI level *
* I did a lot of that a few years back ... but I find as I've gotten older my brain has filled up -- every time I learn a new technology, my brain forgets one that I already know (knew). CoBOL, Pascal, RPG ... BASIC, Perl, Objective-C ... What are those?
Anyway let me know by PM or on an AI thread, here -- when I can help!
When I posted earlier on this thread that "this changes everything" -- little did I know that it also applied to Apple's Swift 2.0 syntax, structure and implementation :no:
None of my existing Swift apps even compile anymore ... Back to being a Swift Noob, with few places to seek assistance.
At least I got my wish on Swift going Open Source, eh Dick?
The more Swift matures the more it takes from ObjC/C which makes me even more happy.
I keep reading on several blogs/sites about the Google Go language so I'll be blunt: Outside of Google and a few FOSS stalwart fans of theirs no one within the LLVM Ecosystem could give a **** about Go.
Swift will be huge.
I just wish they would incorporate a little more of the functional paradigm from Scala.
Just small things annoy me like "If else" not being a function, "switch"/"match" not being a function and returning a value.... and I would like them to make the "return" keyword optional.... the last executed line of a function is the return value.
I keep reading on several blogs/sites about the Google Go language so I'll be blunt: Outside of Google and a few FOSS stalwart fans of theirs no one within the LLVM Ecosystem could give a **** about Go.
Swift will be huge.
I just wish they would incorporate a little more of the functional paradigm from Scala.
Just small things annoy me like "If else" not being a function, "switch"/"match" not being a function and returning a value.... and I would like them to make the "return" keyword optional.... the last executed line of a function is the return value.
I am certainly no Swift expert, but couldn't you implement those with extensions or some such?
I realize that's not as satisfactory as having it encapsulated in the language ...
Though, I get the impression that Lattner and his team are quit open to improving the language -- things like:
try/catch
print instead of println
markdown
You might consider filing a feature request -- especially before it goes open source!
At least I got my wish on Swift going Open Source, eh Dick?
The more Swift matures the more it takes from ObjC/C which makes me even more happy.
Me too! I really tried learn ObjC -- but never got comfortable with the syntax and seeming, everyone, has his own esoteric version of Best Coding practices!
I think one of the most promising potentials of Swift is to simplify the effort to create frequently-used/commonly-used constructs such as a lists/tableviews.
You could encapsulate these in something like a JSON packet that contained everything needed to display, access, update and manipulate the content ...
no delegates or datasources, no populating table rows/cells, no updating/saving the data ...
Just drag that that little capsule to the Storyboard or Playground and it self exposes it's content if you want to customize it ... otherwise it just works!
If people like this were around when we just grunted, someone would start uttering words... and the others would wave oh my god wrong.... grunt grunt grunt. " src="http://forums-files.appleinsider.com/images/smilies//lol.gif" />
Google Go is older and and has much more cross-platform support at this point. Otherwise, they'd make their own language. Google loves developing nerdy backend stuff as much as Apple likes selling things. Swift is fundamentally designed to remain compatible with ObjC, Google would make something compatible with Java.
Swift, if anything, is "fundamentally designed" to replace Objective-C otherwise they would continue using Objective-C which is 100% compatible! Swift has to remain compatible, for now, in order to be practically useable for Apple's existing developers but I expect that in the not too distant future Objective-C will be deprecated as a new development language by Apple. They did it with Pascal (the original Macintosh's API language) by introducing Carbon to allow pre-OS X code to continue running under Cocoa but then Apple deprecated Carbon.
Swift is the future of Apple programming. Objective-C is a dead (or at least, terminally ill) man walking.
Comments
Everything gets verbified if you're not careful.
Great! Did you come up with that yourself?
Swift is similiar to Python but lucky, Swift lets you have curly braces which makes pretty formatting easier. I am a messy coder and I like when I am done, I do the pretty format and it makes it look pretty and follows the conventions.
Here's a online Swift Playground implementation:
http://www.swiftstub.com
SwiftStub
I could see Apple offering an online service that included all the Apple Swift APIs.
Thank you so much, I dedicated one of my Jetson boards specifically for Swift. I can't wait until either CodeEnvy or Cloud 9, cloud based IDE web apps start supporting Swift. I don't mind using a local IDE for now but when I start to do real projects I really want to do it in the cloud. I've found by making a lot of my projects available to the public I get a lot of assistance from others, which helps me learn faster and develop more applications. Besides, CodeEnvy has become one of the best IDE's I've used, local, cloud or otherwise. This is going to be a lot of fun, I just love playing with stuff like this. First thing I need to do is start writing some API's for CUDA as it has become really important to my projects, I am able to produce better, faster GPU excelerated applications using CUDA than with OpenCL at the moment as the amount of code, libraries, applications in which to plunder for choice code easily outnumbers OpenCL 100 to 1, again, at this moment, it's getting better all the time for Open CL
Anyway thank you for the link, would you be interested in helping me create a thread here in which it's sole purpose is to help us be the best darn Swift programmers possible.
Love to join you and contribute any way I can ...
My stuff will be Apple-oriented, and hopefully, at a higher level than drivers or flogging 'Nix at the CLI level *
* I did a lot of that a few years back ... but I find as I've gotten older my brain has filled up -- every time I learn a new technology, my brain forgets one that I already know (knew). CoBOL, Pascal, RPG ... BASIC, Perl, Objective-C ... What are those?
Anyway let me know by PM or on an AI thread, here -- when I can help!
When I posted earlier on this thread that "this changes everything" -- little did I know that it also applied to Apple's Swift 2.0 syntax, structure and implementation :no:
None of my existing Swift apps even compile anymore ... Back to being a Swift Noob, with few places to seek assistance.
* I did a lot of that a few years back ... but I find as I've gotten older my brain has filled up -- every time I learn a new technology, my brain forgets one that I already know (knew). CoBOL, Pascal, RPG ... BASIC, Perl, Objective-C ... What are those?
None of my existing Swift apps even compile anymore ... Back to being a Swift Noob, with few places to seek assistance.
Well, I can include in my <old> language list: COBOL, C, C++, Pascal, RPG II, BASIC, Foxpro, 8086 Assembly, Objective-C, Java
And Scala, Swift on my new one.
The 1.2 to 2.0 code migration failed that badly????
Swift will be huge.
At least I got my wish on Swift going Open Source, eh Dick?
The more Swift matures the more it takes from ObjC/C which makes me even more happy.
I keep reading on several blogs/sites about the Google Go language so I'll be blunt: Outside of Google and a few FOSS stalwart fans of theirs no one within the LLVM Ecosystem could give a **** about Go.
Swift will be huge.
I just wish they would incorporate a little more of the functional paradigm from Scala.
Just small things annoy me like "If else" not being a function, "switch"/"match" not being a function and returning a value.... and I would like them to make the "return" keyword optional.... the last executed line of a function is the return value.
I am certainly no Swift expert, but couldn't you implement those with extensions or some such?
I realize that's not as satisfactory as having it encapsulated in the language ...
Though, I get the impression that Lattner and his team are quit open to improving the language -- things like:
You might consider filing a feature request -- especially before it goes open source!
Me too! I really tried learn ObjC -- but never got comfortable with the syntax and seeming, everyone, has his own esoteric version of Best Coding practices!
I think one of the most promising potentials of Swift is to simplify the effort to create frequently-used/commonly-used constructs such as a lists/tableviews.
You could encapsulate these in something like a JSON packet that contained everything needed to display, access, update and manipulate the content ...
no delegates or datasources, no populating table rows/cells, no updating/saving the data ...
Just drag that that little capsule to the Storyboard or Playground and it self exposes it's content if you want to customize it ... otherwise it just works!
Let's just go ahead and everything it.
Let's just go ahead and everything it.
If people like this were around when we just grunted, someone would start uttering words... and the others would wave oh my god wrong.... grunt grunt grunt.
" src="http://forums-files.appleinsider.com/images/smilies//lol.gif" />
Google Go is older and and has much more cross-platform support at this point. Otherwise, they'd make their own language. Google loves developing nerdy backend stuff as much as Apple likes selling things. Swift is fundamentally designed to remain compatible with ObjC, Google would make something compatible with Java.
Swift, if anything, is "fundamentally designed" to replace Objective-C otherwise they would continue using Objective-C which is 100% compatible! Swift has to remain compatible, for now, in order to be practically useable for Apple's existing developers but I expect that in the not too distant future Objective-C will be deprecated as a new development language by Apple. They did it with Pascal (the original Macintosh's API language) by introducing Carbon to allow pre-OS X code to continue running under Cocoa but then Apple deprecated Carbon.
Swift is the future of Apple programming. Objective-C is a dead (or at least, terminally ill) man walking.