-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The deployed Dokka HTML is empty #26
Comments
Seems to be related to Kotlin/dokka#2024 |
Yeah, there is something broken about the Dokka build right now -- I was unable to diagnose the issue, despite having wrestled with Gradle and Dokka for many hours. I'm not actually sure if this is Dokka or Gradle's fault. To be honest, despite having used Gradle for almost a decade, it's a mystery to me how anything works at all. As far as I can tell it's like TeX -- there is no reason, just Google, trial and error. |
I quite agree with you about Gradle... I personally understand around 30 classes from the Gradle core. |
I am going to be honest because I really do enjoy many things about Kotlin. By far the most painful part of working in Kotlin today is the build system. When Hans pitched the Kotlin team about integrating @gradle ~8 years ago, I thought it was a mistake then and I am even more convinced now. If Kotlin really is interested in broader adoption and language usability, someone needs to make some hard choices to simplify or rethink their build process. It's incomprehensible. I don't have any more constructive feedback, but they might consider taking some ideas from OCaml's module system or Rust Crates. |
The deployed documentation site is empty (I'll try to investigate this on my own, just reporting).
http://breandan.net/kotlingrad/
The text was updated successfully, but these errors were encountered: