Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Nix with dynamic derivations (RFC92) could potentially beat this curse.
https://github.com/NixOS/rfcs/blob/master/rfcs/0092-plan-dyn...
I recently wrote Hancho (https://github.com/aappleby/Hancho) that is designed to be fully dynamic; I thiiiink it would fit most of the desired criteria here (aside from cloud caching) but I'm not positive.
I'll have to do a bit more investigating into what this article means by "dynamic dependencies".
> Rig is not that yet, unfortunately. I don't want to get your hopes up.
No worries, this space has so much inefficiency that I'm sure you will eventually start chipping away at it.
> Can you describe the friction and its source? I'll do some rethinking and redesign.
Some software ecosystems already have their own build tools. Often these build systems are intertwined with IDE support. So care must be taken to ensure the IDE still functions as developers expect. If you ignore the functioning of the IDE, developers will balk at adopting the new build tool. There is some prior art for generating files that an IDE can understand:
https://buck.build/command/project.html
https://github.com/bazelbuild/tulsi
Interfacing existing build tools into a meta build tool can be difficult to do efficiently, but I’ve run out of time for talking about that tonight.