> What the hell is there to complain about, would you rather work in 50+ year old cobol?
I'd rather work on modern AND stable language (I actually do, its not Swift, buy that's not my point). Broken code samples is a good reason to complain. Swift is a moving target, it will be for a while, and this is real pain... but its not a secret. If it bothers someone, why would they choose to use it?
Re:Swift Changes Considered Harmful
by lordnaikon on Sunday February 19, 2017 @03:42AM
(#13678772)
> I'd rather work on modern AND stable language (I actually do, its not Swift, buy that's not my point)
Greetings fellow Rust user ;)
Re:Swift Changes Considered Harmful
by mike_hearn on Saturday February 18, 2017 @05:37PM
(#13677080)
You make it sound like what Swift does is inevitable. Kotlin is of a comparable age to Swift (both started in 2010) and has reached 1.0, which they now plan to maintain Java-like levels of compatibility with. The 1.1 release that's about to come out more or less does that. Certainly any example code you find on the internet today is likely to work fine.
Swift reminds me of java/C++ in the early days. Consumed a lot of memory, the JVM was slow, C++ compilers were janky and so on. Swift is definitely an unstable language although, and it has a lot of performance and stability improvements that need to be done with the debugger, source kit and compiler.
But this will all be fixed in time, in about 4-5 years I'm guessing. It still is definitely a beta language.
Swift work was started 4 years before release, so it's actually a 3+4=7 year language. Every language seems to need a decade before you could call it a stable language I've found, so we have 3 or 4 more years of instability left.
Cyanide is considered harmful. Opinions are just opinions, but calling something harmful when you just don't like it should be considered silly.