News for hackers. Stuff that matters.
Re:Introducing Phoenix, Swift set free by coldtea on Tuesday October 21, 2014 @03:35PM (#8489343)
>There are so many open source languages in the ML family, a few of them are even used in the industry for several years now. Just go and join one of those projects.

Well, some people like the decisions behind Swift, and would prefer a language with an ecosystem, documentation and developer community of the size that results from Apple being involved in it compared to, say, Jane Street.

Heck, people also use Go mostly because of the Google involvement (and the momentum that gives), and it's a language 30 years behind Swift.

Re:Introducing Phoenix, Swift set free by michaelchisari on Tuesday October 21, 2014 @05:44PM (#8490273)
> it's a language 30 years behind Swift.

Interesting idea. Can you post a link that explains why that is?

Re:Introducing Phoenix, Swift set free by coldtea on Tuesday October 21, 2014 @06:41PM (#8490589)
I guess because the Go creators didn't study much (or cared about) the last decades of language research. Heck, the major language they were involved and associated with, C, wasn't that "current" even at the time when it appeared, just pragmatic in a "worse is better" way and readily available. They were every influencial systems guys, with C, Unix, Plan 9, etc, but not really big PL/Compiler guys.

Now, Swift is pragmatic too, and far from cutting edge, but still ways ahead of Go in that area, and its creator is a very strong player in the field of compilers (he also did LLVM).

Here's a link that shows how much hasn't changed:

http://cowlark.com/2009-11-15-go/

Re:Introducing Phoenix, Swift set free by Dewie on Tuesday October 21, 2014 @07:09PM (#8490692)
Robe Pike seems to like to lament the fact that systems research is irrelevant. Well, PL research sure seems to be irrelevant - either something he is largely unaware of, or doesn't feel he needs - to him.
Re:Introducing Phoenix, Swift set free by rsynnott on Tuesday October 21, 2014 @06:43PM (#8490604)
Except for its concurrency model (and it's an open question whether having a concurrency model built right into a language is even a good thing; it's certainly not a no-caveats win), Go is really, really conservative in design. Swift, by contrast, has adopted concepts left right and centre; there's nothing particularly novel, but it's certainly far more adventurous.