3 ms·
Any language designer that has both "modern, powerful features" and "familiar for current developers" as design goals, will end up with something not unlike oth
by skrebbel 12y ago
Any language designer that has both "modern, powerful features" and "familiar for current developers" as design goals, will end up with something not unlike other languages that have this. It is not a coincidence that Scala, modern C#, Kotlin, Xtend, Nemerle, Ceylon, Dart and Swift have a lot in common. They're all compiled languages with pretty high performance characteristics. They have support for OO stuff because of the "familiarity" goal (and, often, to interface with existing code) plus functional stuff because of the "powerful" goal. In a way, they're all Java with suck removed and cool stuff bolted on top.
So can we please stop the "ripoff!" arguments and look at what you can do with it? (note, i'm referring to HN comments on threads about Swift more than to the article)
C# 1 was a blatant ripoff of Java 1.2 (or something like that), with hardly anything new added, and only the biggest suck removed. Look at where C# is now. If Apple can push Swift the same way, there are good times ahead!
(assuming it gets good non-Apple support, but that's another rant)
- Aqueous 12y agoI don't think anyone's saying Swift is a rip-off (or anyone that I know). If anything it compliments both Swift and Scala that the two are so alike.
- TazeTSchnitzel 12y agoI don't think anyone's complaining about the similarity. :)
- seunosewa 12y agoThe development of C# 1 was led by the chief architect of Delphi. It probably got more features from the previous language its creator designed than from Java...
- noblethrasher 12y agoC# 1.0 (the spec) and especially Visual C# 1.0 (the IDE) were recapitulations of Delphi in Java skin. Now, C# is by far my favorite language (even though I think in ML), but I'm now a bit envious of the Java approach: One of the big ideas of OOP going back to Alan Kay is that OO languages should be extremely dynamic, and that you achieve performance by building better hardware (or tuning it)†. This is what Java and Objective-C do. And, this is why Java programmers can create classes and objects with reckless abandon and still get excellent performance. Meanwhile, in C#, I find myself worrying about whether something should be a class or a struct; it doesn't happen often, and I know that I ought not be thinking about it, but it's there. So, in summary, I now appreciate the value of putting the performance knobs on the machine rather than in the language, which represent the two different philosophies of Java and C#. †Said by Alan Kay, and repeated by Steve Jobs: “People who are really serious about software should make their own hardware.”
- virtualwhys 12y agoWell, it's worth pointing out that Scala pre-dates most of the new comers you mention by several years. Kotlin, for example, their raison d'etre seems to be, "we're Scala without the complexity"[1]. As for the syntatic similarities between Swift and Scala, well, they're not identical (and the whole `var` bit on the Scala side should be chucked out as that is far from idiomatic Scala). At most you can say that Swift is more similar to Scala than any other language, which is to say the language designers probably saw some nice-to-haves in Scala and acted accordingly. For me Swift seems like a kind of hybrid ML Coffeescript a la Scala with a Swist ;-) [1] http://confluence.jetbrains.com/display/Kotlin/Comparison+to+Scala http://confluence.jetbrains.com/display/Kotlin/Comparison+to...