translatenix

@sgammon Yeah I wouldn't write such code. But my point still stands--just take a look at the suggested diff.

There's nothing to compute here unless you're trying to hypothetically save a microsecond. I'm also not aware of any cross-platform issues that `layout.buildDirectory` solves. I think a separate PR is...

@sgammon Would it be possible, and make sense, to use [buildless](https://less.build/) for the Pkl build? Sounds like direct competition for Develocity. And perhaps you could ask your web designer to...

Sounds good. I'm not part of the team, just trying to help where I can.

I think you should demo buildless to the Pkl team!

@bioball Ready from my side.

@bioball CI is failing due to some missing task dependencies on `createTestPackages`. Will send a follow-up PR shortly.

The same problem exists for Java and Kotlin code generation. Gradle users can use the Gradle plugin.

I think the goal should be for tools to communicate with Pkl over the binary protocol. Then each tool can have its own, small native executable.

You actually mean hard link, i.e., `a.pkl` and `b.pkl` point to the same inode? It's normal and expected for hard links and symbolic links to have different semantics. On the...