fewer braces every day - sometimes still useful to use curlies around a long closure.
Other notes - i don’t get bothered if there is a mix of braces/no braces
fewer braces every day - sometimes still useful to use curlies around a long closure.
Other notes - i don’t get bothered if there is a mix of braces/no braces
I find it a bit strange that making syntax more similar to Python, one of the most used programming languages, especially among beginners and non programmers, in the age of AI, should make the code unapproachable for senior Scala developers. That makes me sad to hear.
I think Scala’s way of doing this is superior even to Python, because you cannot error out on the return type, the compiler holds your back all the way.
At scaladays non of the people I talked to complained about the new syntax. I have done training for Java, Kotlin and Typescript developers and everyone found that syntax nice to work with. They spent 0 time getting into it.
Of course, as everything, it takes some time getting used to, but for me at least, it definitively was worth it. Doing some research around how to use the syntax efficiently is welcome of course.
I wonder if these problems maybe could be more related to tooling ? In Elixir you get automatically the ‘end’ marker injected when you create a function or module. In python you can also get your IDE to enforce indentation correctly so you (almost) never have a problem with that. Maybe some experiments with optional configuration in metals could be better time spent. I encourage to test out vscode or Intellij on Elixir or Python and do a comparison.
I hope however, I will not have to spend time on such a poll.