News for hackers. Stuff that matters.
Re:The case against Kotlin by emodendroket on Saturday July 29, 2017 @06:38PM (#14883314)
> First, it took a little time to get the hang of json manipulation. We got to a solution we liked, but a dynamically typed language like groovy has some advantages there.

Does it? I really prefer JSON.NET's approach, which involves declaring models that represent your JSON, over dynamic "hope it's there" approaches.

Re:The case against Kotlin by Guthur on Saturday July 29, 2017 @10:20PM (#14884060)
False equivalence. You can static check this until you ate blue in the face but you still 'hope its there'. You would specify the contract for runtime checking like any sane engineer
Re:The case against Kotlin by emodendroket on Saturday July 29, 2017 @10:44PM (#14884158)
Yes, but I don't have to worry about something like unintentionally spelling it differently on different lines, and in the case where I'm controlling both ends it is truly taken care of for me.