Comment on How we failed, then succeeded, at migrating to TypeScriptparentComments−AriaMinaei6yDon't want to invalidate your experience. For me though, I rarely struggled with ambiguity.function call syntax doesn’t need parens except if a 0 parameter methodFunction call syntax doesn't require parens so to make multi-line calls punctuation-free. Especially if some args are objects.commas are largely optional both in arrays and function parameters. How do you parse: [f, f(), f a b c]Well commas are not optional.implicit returns are a terrible ideaThey're especially elegant in writing declarative code. It takes some getting used to though.the @ syntax refers to either a ‘static’ method or an instance variable depending on the context.Agreed.These are all tradeoffs though. For me, they struck the right balance between ambiguity (very little) and expressiveness.LiveScript in comparison was much more sugary (which I preferred): https://livescript.net/−k__6yHaha, yes. LiveScript should have won. It were awesome times.Well, guess it's Reason for me now :D
Comments
Don't want to invalidate your experience. For me though, I rarely struggled with ambiguity.
Function call syntax doesn't require parens so to make multi-line calls punctuation-free. Especially if some args are objects.
Well commas are not optional.
They're especially elegant in writing declarative code. It takes some getting used to though.
Agreed.
These are all tradeoffs though. For me, they struck the right balance between ambiguity (very little) and expressiveness.
LiveScript in comparison was much more sugary (which I preferred): https://livescript.net/
Haha, yes. LiveScript should have won. It were awesome times.
Well, guess it's Reason for me now :D