4 ms·
It is incredibly risky to release this unto the world without having tryed it internally. I hope they can iterate quickly enough to iron out the most glaring pr
by Derbasti 12y ago
It is incredibly risky to release this unto the world without having tryed it internally. I hope they can iterate quickly enough to iron out the most glaring problems before the language is ossified by the amount of code already written in it.
Otherwise, we might just get stuck with something half-baked that never had a chance of growing up before widespread adoption.
- serge2k 12y agoThen in 20 years people will convert everything under the sun to run in it and claim it's the new assembly.
- acqq 12y agoThe article actually states that all the API's are the old ones. And not so long ago most of the posts here were that Swift is "too conservative." I claim that Swift is very good selection of more modern stuff on the tried and tested base. It doesn't even depend in GC and VM. It's great in its conservativeness.
- interpol_p 12y agoIt seems to have been used internally for some time. The public WWDC app was written in Swift, and many Apple engineers had moved to using Swift entirely by the time it was announced. The most glaring problems exist in the IDE support for the language, not the language itself. There is minuscule risk of Swift not gaining widespread adoption amongst iOS and OS X developers.