Policy – A fork of the Scala compiler
github.com
Policy – A fork of the Scala compiler
1–10 of 119 posts
Re: Policy – A fork of the Scala compiler
#2Can someone with some familiarity with Scala community explain why someone who seems to be the largest contributor to Scala felt the need to create a fork? It seems completely justified due to his credentials, but he doesn't give any specific reasons why he created this fork.
Re: Policy – A fork of the Scala compiler
#3Can someone with some familiarity with Scala community explain why someone who seems to be the largest contributor to Scala felt the need to create a fork? It seems completely justified due to his credentials, but he doesn't give any specific reasons why he created this fork.
Paul Phillips' 2013 rant/talk: https://www.youtube.com/watch?v=TS1lpKBMkgg
Re: Policy – A fork of the Scala compiler
#4Can someone with some familiarity with Scala community explain why someone who seems to be the largest contributor to Scala felt the need to create a fork? It seems completely justified due to his credentials, but he doesn't give any specific reasons why he created this fork.
> "The leadership of scala has shown itself unfit stewards of the core technologies and the total price paid by scala programmers (actual and potential) is too high. I failed for half a decade to change that from the inside. Now I'll try from the outside."
Re: Policy – A fork of the Scala compiler
#5Can someone with some familiarity with Scala community explain why someone who seems to be the largest contributor to Scala felt the need to create a fork? It seems completely justified due to his credentials, but he doesn't give any specific reasons why he created this fork.
The type systems broke him.
Re: Policy – A fork of the Scala compiler
#6Can someone with some familiarity with Scala community explain why someone who seems to be the largest contributor to Scala felt the need to create a fork? It seems completely justified due to his credentials, but he doesn't give any specific reasons why he created this fork.
> "The leadership of scala has shown itself unfit stewards of the core technologies and the total price paid by scala programmers (actual and potential) is too high. I failed for half a decade to change that from the inside. Now I'll try from the outside."
That's a strongly worded statement for a front page, but I wish I knew something more about the situation. What progress is being held back? I've not written a line of Scala myself.
Re: Policy – A fork of the Scala compiler
#7The "A Fork!? You Should Improve Scalac!" section is delightful.
Re: Policy – A fork of the Scala compiler
#8Can someone with some familiarity with Scala community explain why someone who seems to be the largest contributor to Scala felt the need to create a fork? It seems completely justified due to his credentials, but he doesn't give any specific reasons why he created this fork.
Paul Phillips' 2013 rant/talk: https://www.youtube.com/watch?v=TS1lpKBMkgg
[deleted]
Re: Policy – A fork of the Scala compiler
#9Can someone with some familiarity with Scala community explain why someone who seems to be the largest contributor to Scala felt the need to create a fork? It seems completely justified due to his credentials, but he doesn't give any specific reasons why he created this fork.
there is in fact more forking happening:
https://news.ycombinator.com/item?id=8258255
https://news.ycombinator.com/item?id=8261896
_____________________________
Many (most?) of the debates regarding the scalac roadmap (and attendant tooling) happened in public on the internals mailing list. The simplest explanation is that nobody agreed on allocation of resources, which were mostly a few Typesafe employees and some (largely unknown but very talented) EPFL grad students. A sample thread https://groups.google.com/forum/#!msg/scala-internals/9Ts3GL...
Re: Policy – A fork of the Scala compiler
#10Earlier quoted context omitted.
Paul Phillips' 2013 rant/talk: https://www.youtube.com/watch?v=TS1lpKBMkgg
[deleted]
It turns into a rant about how he'd wish the compiler and the editor and the source control should be all talking with one another.
It's funny, because there's actually a language just like that: Smalltalk. The development environment is the same as the runtime environment, it has its own source control (Monticello), its own editor and a very regular language.