Too bad. We'll stay with our groovy hacks. I hope someone will take up the torch. I wish I could, but I've enough on my plate already. Thanks for trying, anyway.

I'm happy to pick up the torch myself again, I have plenty of ideas I didn't get a chance to implement, but I'm not going to do this without traction...

Good to know!

Hi Cedric, I think the main problem with Kobalt was marketing. I'm no expert in that area myself, unfortunately. There definitely is pain around Gradle, though. It's a complicated and mysterious hurdle to any new kotlin project.

Maybe you could repackage parts of Kobalt in Kash? The shell could have a build function (that would consume the mostly declarative build file) but also let you run scripts in the context of your project.

Maybe Kobalt tries to be too similar to gradle when what we really need is a departure, targeted at a completely different market: the pythonistas

Maybe, @pabl0rg. I think Gradle is such a heavyweight that nothing else gets any attention, really. And recently, JetBrains released ki, which seems to have quite a bit of overlap with Kash 🙂

Hi @cedric. Yeah, I saw the ki announcement the day after posting my comment. It would be cool to rework parts of kobalt into a build plugin for ki. The hardest part would probably be IDE compatibility

how does ki compete with kobalt, though?

i keep daydreaming about converting a project or two over to kobalt but I haven't touched kobalt in a long time. 😞

Neither have I 😞

I’ve been on a Rust binge lately

i did advent of code with rust. didn't finish because i got busy but it was fun to play with.

Bump, I'm rediscovering my profound hatred of problems with gradle. I'm converting two not-particularly-large projects to gradle, one is very straightforward and the other involves some polyglot stuff. Both have been converted from groovy-gradle to kotlin-gradle, and Im still making very slow and very painful progress. I wrote myself a little manifesto basically describing my problems with gradle and what I would replace them with, and I realized that im mostly in line with kobalt. If I werent at a broke startup I might try contributing to kobalt.

-sigh- Preach on 🙂

I am actually writing a Kotlin/Rust article as we speak and I just finished the cargo/gradle comparison. Let's just say that Gradle doesn't come out of it in a very good light 🙂

Funny, I almost ended up with a job at mozilla working with rust. I kinda wish I'd pressed harder for it, it seems like a very cool eco system.

Here is part 1 if you're curious: https://www.beust.com/weblog/2021/10/20/what-rust-could-learn-from-kotlin/

And yes, Rust is surprisingly fun

I cant help but feel like gradle would rather be performant than correct

my copy task hangs gradle

In case anyone interested, I started playing with kobalt, currently on my own fork: https://github.com/oshai/kobalt I released a new version

1.1.7

to https://github.com/oshai/kobalt/releases and added instructions how to use it: https://github.com/oshai/kobalt#manually At first step I plan to do upgrades/cleanups (jcenter etc') Later I want to experiment with dependencies (locks, resolution), add support for direct maven central deployment / github actions and migrate my projects to use it.

@cedric I have a few questions, while trying to compile/test kobalt: • I am running

./kobaltw clean compile test --sequential

and some tests fails / fails to configure. Is there any setup I should do before? • Is there any reason the repo contains src and modules? it seems modules/kobalt just points the src dir? • The repo contains both gradle/maven/kobalt configuration. which is the recommended one to use? I guess kobalt is the most recent one? Mostly for the sake of running tests in intellij.

Not sure about the test failure, missing file... I'd have to go back and look at that test

I also had to fix other tests. I can send that as a PR is you want.

Sure!

at the moment I am trying to debug two tests that fails only sporadically, when I run all the tests. It looks like some kind of race condition in the build.

the log from such failure is here: https://gist.github.com/oshai/72dc87c58090dbd58dcefb8625df9196

error is

ERROR Error: com.beust.kobalt.KobaltException: Invalid classpath: couldn't find /var/folders/f9/c2brg7yx24gftgpb49rpf3jw00p91s/T/kobaltBuild/classes

it looks like something which is not getting cleaned as expected, so I am not sure so interesting