Should this not already be part of the syntax discussions, would it be possible for arbitrary choices to default on the result on the few empirical studies that have been made in this area?
e.g.
Nothing immediately actionable here, but this is one of the biggest things Reason enables: allowing us to freely experiment on new syntaxes, empirically, without breaking code. Somewhat related: I myself am a fan of Koka, Red and Kitten's syntax. Now we'll actually have a chance to take their best sugars and try them in some future alpha Reason releases for the adventurous ones, while others stay with the stable Reason syntax (or their own flavor of it, who knows...) and keep coding. Exciting future ahead.
However, because there's nothing immediately actionable, I'll close this for now. Thanks for the paper and we'll keep this in mind! =]
I just read the abstract and it sounds fascinating. One thing to consider is that Reason's goal is to reach out to the majority of industrial programmers, not necessarily first time programmers. Experienced industrial programmers have already become tainted, such that syntaxes that are empirically worse for beginners, may be easier for those experienced people to pick up quickly. I would love to see a similar experiment done on experienced programmers.
Most helpful comment
Nothing immediately actionable here, but this is one of the biggest things Reason enables: allowing us to freely experiment on new syntaxes, empirically, without breaking code. Somewhat related: I myself am a fan of Koka, Red and Kitten's syntax. Now we'll actually have a chance to take their best sugars and try them in some future alpha Reason releases for the adventurous ones, while others stay with the stable Reason syntax (or their own flavor of it, who knows...) and keep coding. Exciting future ahead.
However, because there's nothing immediately actionable, I'll close this for now. Thanks for the paper and we'll keep this in mind! =]