Chances are they aren't a technical person and didn't build it, so wouldn't have anything interesting to say anyways. Web compilers are dime-a-dozen and LLMs can easily produce them with no active guidance. Very much in the training data[1]. This looks like just another person posting something they spent all of two minutes prompting.
So, is there a reason that your link to the official playground is dramatically more underwhelming and lacking in features compared to the from-scratch-in-C Minikotlin compiler page? You claim that the submission is uninteresting work from a lone non-technical rando and then link to / implicitly endorse a "hello world" repo from the multi-billion dollar corporation that runs the whole thing?
The JetBrains team didn't feel like prompting for a Claude UI to go with their project they wrote by hand 8 years ago, I suppose.
Are you really that impressed with stock LLM-generated UI?
Note the JetBrains one includes features that are actually useful for a code playground, letting you configure compiler version and flags, which is likely more relevant than a faux-IDE UI for the use cases people use playgrounds for. The JetBrains playground also supports importing packages, which this doesn't. This doesn't seem like a human even attempted to use it for anything, otherwise they would have realised how lacking it is. Unfortunately it seems like people who prompt slop can't be bothered to dogfood it... or maybe pigfood it?
It's on my todo list to support compiling dart code through the wasm bundle to wasm directly. Right now it's running the dart arm simulator on the web because it supports hot reload.
I'm wondering if there are any cool use-cases that motivate having the compiler itself run in wasm. I did it mostly for fun and besides building tooling for compiler developers themselves or IDEs, I can't come up with much.
There was one guy that wanted a sandboxed environment for agents as he couldn't find anything else. A few other people used the dart live project to build playgrounds for their own packages.
Who's the target audience for minikotlin? I'm just curious.
Cool idea. I like the UI and that it compiles locally. But I don't really get what this is for.
I use Kotlin Playground sometimes, but it allows me to switch Kotlin versions and compile targets, which is useful to try out new features.
That's cool. I often write tiny blurbs of kotlin just to test out a simple algorithm. I often do this on kotlin playground because doing so inside a scratch file or test is somehow more cumbersome and slow. This ran and compiled something in 98ms on my smartphone, cool stuff.
Visibly claude produced website. No link to code.
Is the expectation that people write kotlin in their browser? How do people work this into their development workflow? Is this just a neat demo?
I was expecting a a link to the source code after the "written in C".
Yeah, I hate the LLM wording too
This is very cool! Slightly off-topic though, I miss technical people writing in their own voice about the awesome things they've built.
Chances are they aren't a technical person and didn't build it, so wouldn't have anything interesting to say anyways. Web compilers are dime-a-dozen and LLMs can easily produce them with no active guidance. Very much in the training data[1]. This looks like just another person posting something they spent all of two minutes prompting.
[1] https://github.com/JetBrains/kotlin-playground
So, is there a reason that your link to the official playground is dramatically more underwhelming and lacking in features compared to the from-scratch-in-C Minikotlin compiler page? You claim that the submission is uninteresting work from a lone non-technical rando and then link to / implicitly endorse a "hello world" repo from the multi-billion dollar corporation that runs the whole thing?
The JetBrains team didn't feel like prompting for a Claude UI to go with their project they wrote by hand 8 years ago, I suppose. Are you really that impressed with stock LLM-generated UI?
Note the JetBrains one includes features that are actually useful for a code playground, letting you configure compiler version and flags, which is likely more relevant than a faux-IDE UI for the use cases people use playgrounds for. The JetBrains playground also supports importing packages, which this doesn't. This doesn't seem like a human even attempted to use it for anything, otherwise they would have realised how lacking it is. Unfortunately it seems like people who prompt slop can't be bothered to dogfood it... or maybe pigfood it?
"From scratch in C" means literally nothing here.
I built something similar, but I managed to compile the Dart VM, its compiler and the static analyzer to wasm using emscripten:
- repo: https://github.com/modulovalue/dart-live
- demo: https://modulovalue.com/dart-live/
It's on my todo list to support compiling dart code through the wasm bundle to wasm directly. Right now it's running the dart arm simulator on the web because it supports hot reload.
I'm wondering if there are any cool use-cases that motivate having the compiler itself run in wasm. I did it mostly for fun and besides building tooling for compiler developers themselves or IDEs, I can't come up with much.
There was one guy that wanted a sandboxed environment for agents as he couldn't find anything else. A few other people used the dart live project to build playgrounds for their own packages.
Who's the target audience for minikotlin? I'm just curious.
In any case, cool project, thanks for sharing!
Seems to be missing the "why" over Kotlins native WASM support (which is very mature)
The official Kotlin playground uses WASM, for example (JVM drop down-> choose "WASM")
https://play.kotlinlang.org
I think that compiles WASM in the server, whereas this compiles in the browser.
I'd challenge the 'by hand' assertion though.
Cool idea. I like the UI and that it compiles locally. But I don't really get what this is for. I use Kotlin Playground sometimes, but it allows me to switch Kotlin versions and compile targets, which is useful to try out new features.
That's cool. I often write tiny blurbs of kotlin just to test out a simple algorithm. I often do this on kotlin playground because doing so inside a scratch file or test is somehow more cumbersome and slow. This ran and compiled something in 98ms on my smartphone, cool stuff.