dietlibc VS otf

- Dietlibc: https://www.fefe.de/dietlibc/

The commercial success of a product totally depends on the business model you come up with, whatever be its opensource (or not) license.

Corporates have a vested interest in promoting the propaganda that only a non-xGPL opensource license can be commercialised successfully simply because they cannot freely steal the source code of a competing xGPL licensed software.

The real value of an FSF license, like the AGPL, is that it was designed to protect the copyright holders, and its users, "right to repair". And thus, it cannot be closed source by anyone (apart from the original copyright holders) once released under the said license (even if future versions are closed source, the old version under xPL remain opensource perpetually). Other open source license (that are less stringent) are prioritised to increase developer contribution. Source code under such license can be closed-source even from the original copyright holder.

But again, commercial success totally depends on the business model you come up with, irrespective of your license. The right license and the right business model will empower each other. Or cripple your business.

Stefan Tomanek - Creator of dietlibc, a libc optimized for small size - https://github.com/stefan-tomanek (The dietlibc project itself doesn't have an official GitHub repository, but you can find it at https://www.fefe.de/dietlibc/)

There are definitely some nice alternatives to glibc out there. He mentions Cosmopolitan Libc. I've used musl, uclibc, and dietlibc/libowfat in the past.

Maybe you should include the math part of a libc statically with your code. glibc is one option, or dietlibc if you want it to be as small as possible.

I agree that the implementation of printf is complex, but the interface is not. Hence calling it should not introduce bloat. Glibc adds a bunch of constructors and tables and such, whereas linking with dietlibc will probably lead to a smaller executable.

Not to be confused with OTF which is the open source version of Terraform Enterprise:

https://github.com/leg100/otf

[2]: https://github.com/leg100/otf

I wonder if a non commercial Terraform Cloud "offering" like https://github.com/leg100/otf is "competing" with Hashicorp...

I've built an [open source clone](https://github.com/leg100/otf) of terraform cloud. Will it contravene BSL?

(1) Under the hood, it forks the terraform binary.

Hey everyone — I’ve been building an open-source Terraform Cloud/Enterprise alternative and I just released the first (alpha) version: https://github.com/hatchet-dev/hatchet. I’ve enjoyed seeing the recent OSS alternatives popping up (OTF, Terrakube, Terrateam) and wanted to put this out there as well.

>https://github.com/leg100/otf