News for hackers. Stuff that matters.
Re:The case against Kotlin by eropple on Saturday July 29, 2017 @07:12PM (#14883459)
What trouble did you run into with JSON? I just make Jackson objects as data classes and I'm done with it. Mucking with ObjectNode/ArrayNode is a bit annoying but not too bad, especially when you can map and collect.

Was gonna say what you did about testing, but you have it, so, yeah. ;)

Re:The case against Kotlin by ebiester on Tuesday August 01, 2017 @02:35PM (#14903869)
Short answer is the presence or absence of a field can drive us to different paths in the code base. That can lead to code littered with !! and @JsonIgnoreProperties(ignoreUnknown=true), or multiple intermediary data classes, or similar solutions. For much of our problem space, an extra val or two and some well placed ifs get us out of it.