> The article shows some examples where you can choose between regular brackets or curly brackets. There's a lot of different ways to say the exact same thing.

> The article shows some examples where you can choose between regular brackets or curly brackets. There's a lot of different ways to say the exact same thing. Why? Which is best? Are there any cases where one works but the other doesn't, and if so, why does the other exist? Yes, but which one would you remove? If you disallowed the curly ones, developers would suddenly require an additional language feature to define methods which could be used like this: using(someResource) { // do something with ressource } Apart from that {} has semicolon inference, while () doesn't. That's extremely helpful, if you have some expression and really want to make sure that it can't be split into something like { doThing1, doThing2 } by an unaware developer. > Total type safety is a trap. Sure, there are limits on what can be done with a type system, but these options have been growing larger and larger in the last decades. I wouldn't throw away the last 40 years of progress in that area and start doing stuff manually which any decent compiler can figure out for me. > Groovy I haven't heard from Groovy since a long time ago. Is it still actively developed? The last things I saw was that they were struggling to catch up, and work on the new MOP still wasn't finished. On the Gartner PLI, Groovy is way down on position 20. That doesn't look too promising either ...