<div dir="ltr">Most source breaking changes will be made in Swift 3. From now on code should be mostly backwards compatible.</div><br><div class="gmail_quote"><div dir="ltr">On Wed, Jul 6, 2016 at 11:28 AM Ted F.A. van Gaalen via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi there<br>
<br>
>From the perspective from many active programmers<br>
that use Swift (not objective C anymore) I am not<br>
very happy by having to change<br>
program source all the time:<br>
<br>
Therefore after Swift 3.0 is released I’d recommend kindly:<br>
<br>
<br>
Freeze Swift For Some Time!<br>
Do Not Change AnyThing For At Least 2 Years.<br>
(Yes you’ve read that correctly: two years.)<br>
<br>
Still there? OK, read on:<br>
<br>
In the mean time, you’ll have the great opportunity<br>
to fine-tune compiler and run time systems, to eliminate<br>
the few bugs there and make it blazingly fast!<br>
<br>
In two (or more) years, there are enough Real Users (programmers)<br>
that by then will have enough practical experience with Swift, which<br>
might play a more solid role in improving Swift, and of course,<br>
are extremely happy with Swift, and that it is not changed<br>
all the time, So that they can concentrate on writing cool,<br>
reliable and decent programs, instead of revising it all<br>
the time!<br>
<br>
After such time, and much more intensive and practical usage,<br>
it becomes clear, what is good in Swift and what is not.<br>
What happens now, for instance, is that some base their “statistics” of which<br>
language elements etc. are frequently used or not, merely upon scanning<br>
a codebase of the relatively few (compared with e.g. ObjC, Java or C#) programmers<br>
that use Swift now<br>
<br>
Imho, Swift has not yet been in use long enough. It needs a prolonged time<br>
because now, most users have relatively little experience using Swift,<br>
thus the way they program now is not really representative with what one really can do<br>
with this powerful language, compared to experienced (years, not months)<br>
programmers in other languages.<br>
Still a lot has to be discovered, has to settle and form good mental pictures in<br>
programmer’s minds. It is all going a bit too fast, I think.<br>
<br>
<br>
Please (if you did’t already) realize that already many source<br>
code all over the world is written in Swift therefore it is very, very<br>
important that backwards compatibility should be preserved as much<br>
as possible. because backwards-breaking-changes are a disaster<br>
to companies/individuals that have already hundreds or thousands<br>
of programs written in Swift.<br>
<br>
For comparison, until recently I did also programming projects on IBM<br>
mainframes for banks, insurance companies etc. The systems they use consists<br>
(per company) of literally thousands of Cobol and/or PL/1 programs written<br>
in all the years from ca 1970 until now. Still, one can take a program written<br>
in 1970 which compiles and runs flawlessly without any modification!<br>
All is backward compatible. If you would break backward<br>
compatibility in this domain you would probably be kicked of the planet..<br>
<br>
<br>
But even if we remain in macOS or iOS development, a huge amount of source<br>
code has been written in Objective C. Everyone would scream hell if you took<br>
out or change language elements..<br>
So please don’t. (it’s unnecessary)<br>
<br>
<br>
When Swift arrived, to me, it had already everything I need, not really missing anything.<br>
Of course, a programming language -like all things in life- is never perfect.<br>
<br>
To me it was also perfectly OK that Swift wasn’t open source, because those that<br>
have made Swift did a very good job. So one could even start thinking, why<br>
open source Swift? Why not leave it to Apple?<br>
But I guess I won’t make many friends asking this..<br>
And I also realize that many good ideas comes from open source.<br>
<br>
<br>
To me, Swift 2.2 and also 3.0 is fine.<br>
so, after that:<br>
you don’t have to change a thing.<br>
it works and has everything I need<br>
and is fast and stable.<br>
stop removing things.<br>
thanks.<br>
<br>
<br>
Kind Regards from beautiful Speyer.de in Germany<br>
<br>
TedvG<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div><div dir="ltr">-- <br></div><div data-smartmail="gmail_signature"><div dir="ltr">-Saagar Jha</div></div>