Wow 😮 That’s awesome: https://github.com/kennycason/genetic_draw by @kennycason Description: http://kennycason.com/posts/2016-06-01-genetic-algorithm-draw-images.html

I started to write last week a post on genetic algorithm in kotlin 😉

I have tested the Kenny’s program

and it’s pretty amazing

simple idea wrap SLF4J inside a kotlin wrapper to allow passing lambdas and avoid possibly costly arguments computation if the priority is high

The Destructor Pattern by @domfox https://opencredo.com/the-destructor-pattern/

JVM language activity, good figures for Kotlin: https://github.com/slurpdurp/nogood/wiki/JVM-language-activity

A Kotlin toolkit for Mongo http://litote.org/kmongo/

A handful of Kotlin permutations https://medium.com/@voddan/a-handful-of-kotlin-permutations-7659c555d421#.zah77m5ii

I've improved

kscript

to also work with inline scripts. See https://github.com/holgerbrandl/kscript#inline-usage

Thoughts of @mikehearn about Kotlin Native https://medium.com/@octskyward/kotlin-native-310ffac94af2#.h712ac5hr Are you agree?

Data wrangling with kotlin using krangl http://holgerbrandl.github.io/krangl/krangl_intro/krangl_intro.html or directly checkout the repo https://github.com/holgerbrandl/krangl

@roman.belov: Interesting post, even if I am not sure to agree with the conclusion 😉 I have added a comment about WebAssembly.

@sdeleuze: thanks, I have recommended your response

i must admit, i find myself unconvinced by WebAssembly

i remember mozilla rejecting a google project to put a modified jvm into the browser, one that enforced the same-origin policy approach and used the DOM as the UI (not java applets)

their reasoning wasn't very good

now the idea is back, but with JIT compiled C/C++ this time. ah well. the web needs some competition 🙂

@mikehearn: I hope you will be more convinced at the end of the year 😉 I think WebAssembly is the result of many previous attempts : native client, asm.js, GWT, Dart but also Java applets, Flex, Haxe, etc. A lot of lessons have been learnt, and this time it seems the big ones all play together, which is really something new. MVP is mostly C/C++ centric but what will be interesting to see is what occurs post MVP. WebAssembly is not fixed in stone yet, and languages like Swift or Kotlin could significantly impact what WebAssembly will be if the catch the train now. In any case, I prefer a clean bytecode approach that exposes DOM and Web APIs (even if this is a long road) without having to transpile to JS, which is a hack full of traps ...

it is certainly better than transpilation

wow. after the hacker news link, my article on kotlin is now in the 3rd place in google search results