406 karma · joined February 21, 2015
And the linux build must be requested from discord: https://lmstudio.ai/
Using "chance of occurrence" is a major logical fallacy for diagnosis identification and can ruin the whole practice.
1. IaC description should be format agnostic and transformable (eg definable in yaml, json, whatever).
2. Something about provider interfaces here, but it's already super messy and not sure if it's an improvement or just a shift
3. State files were wild west last time I checked. And there should be a default database interface provider at minimum. Maybe there is now?
4. Forcing the apply->statefile cycle as the default requires all of compute, interface, and a human. This should have been an abstraction on a raw interface for automated use.
Like it or not, cohorts of engineering organizations like the above (cloud providers) have a very outsized weight and already have contender products they can choose to vigorously fund tomorrow.
From the article:
The license does not allow you to use Terraform if you meet both of the following conditions: You are building a product that is competitive with HashiCorp. You embed or host Terraform in your product.
My $0.02: the management of hashicorp is following a stupid trend and should have thought about their customers more.
It will come out to what lawyers think, I guess. Lawyers usually say no to things with poorly established precedent.