Frontend Kotlin from the Trenches
summary
A data-visualization library is implemented in Kotlin and compiled to JS, using Gradle for builds, Karma+PhantomJS+Mocha for JS tests and JVM multi-platform modules to run/debug tests on the JVM. sourcemap embed sources makes Chrome debugging map back to Kotlin. Dead-code elimination plus Webpack+Uglify shrinks an initial ~1.5 MB Kotlin JS runtime to a 197 KB bundle (~50 KB gzipped). Performance of Kotlin-compiled code is about 10% slower than equivalent d3.js; interoperability and missing JS libraries remain pain points.
AI-written summary · about
chapters (15)
- 0:00Start
- 2:19Radio Stacked Bar Chart
- 4:29Do You Consider Yourself as a Front-End Developer a Back-End Developer or Full-Stack Developer
- 13:39Synchronous Module Definition
- 16:39Debugging
- 18:01Sourcemap Embed Sources
- 22:42Package Json Files
- 23:06Test Script
- 24:49Multi-Platform
- 28:33Optimization of the Code
- 28:52Code Elimination Tool
- 31:11Webpack
- 31:22Uglify
- 39:52Weaknesses
- 40:41Interoperability
related talks
43mThe State of Kotlin JS
41mKotlin/JS, Today and Tomorrow
01h 01mKotlin as a Language for Frontend Development
34mIntegrating Kotlin/JS in a Kotlin Multiplatform library
33mUsing Kotlin for JS Client and JVM Server
45mKotlin Fullstack
39mA TypeScript Fan's KotlinJS Adventures
22mKotlin/JS in 1.4 and Beyond