Colloidal

joined 4 weeks ago
[–] [email protected] 13 points 6 hours ago* (last edited 6 hours ago) (1 children)

~~functional~~ programmers when they look at their code 2 years later

FTFY

[–] [email protected] 3 points 8 hours ago (1 children)

Seems like it it isn’t related to Silverlight at all.

[–] [email protected] 1 points 9 hours ago

First of all thank you for your thoughtful response. I do disagree on a few key points though:

The terms of the MPL and BSL are incompatible, insofar that Hashicorp cannot unilaterally relicense MPL code from OpenTofu into BSL code in Terraform. But Hashicorp could still use/incorporate OpenTofu MPL code into Terraform, provided that they honor the rest of the obligations of the MPL.

When you can still use code from a license and distribute the end result under a different license, that means they are compatible. Just like the MIT is compatible with any other license.

if OpenTofu starts to gain new features that Terrarform doesn’t have, Hashicorp can incorporate those features but they won’t be unique.

So they are benefiting from improvements made in OpenTofu.

Why would a paying customer give money to Hashicorp for something that OpenTofu provides for free?

To access the features that are exclusive to Terraform. Companies spend unglodly amounts of money to pay for MS Sharepoint (completely different product, just giving an example of an expensive product with competitive groupware options in the market). Why wouldn't they pay for Terraform, especially if it included a support contract? I think you are severely underestimating the willingness of customers to pay for service if you don't think that would happen.

And all features henceforth developed for Terraform would be exclusive to it, while all features developed for OpenTofu would be available to Terraform because the MPL is such a pushover license that doing so is trivial. OpenTofu will always stay behind in this scheme. In other words, any developer contributing to OpenTofu is donating work to IBM. I bet they are more than okay with that.

Had they moved new OpenTofu contributions to a strong copyleft license, OpenTofu would lose nothing, while Hashicorp/IBM would lose the freeloading of FOSS developer's contributions. IBM still has an out in this scenario, which is offering services to paying customers, just like Hashicorp did before the licensing fiasco. It's a lucrative business model, and one they are good at.

[–] [email protected] 2 points 1 day ago

Like an .ini file.

[–] [email protected] 0 points 1 day ago (2 children)

I didn’t say that, go strawman someone else. Shoo, troll, shoo!

[–] [email protected] 2 points 1 day ago (2 children)

I don’t get it. Why go through the trouble and stay in a license that still allows Hashicorp / IBM to benefit from community contributions?

[–] [email protected] 2 points 2 days ago

What about it makes it 2D?

[–] [email protected] 13 points 2 days ago (1 children)

Do we have a c/keming?

[–] [email protected] 4 points 2 days ago (4 children)

You really can't see the irony of an article praising the "brilliant display" of the unit while simultaneously erasing what makes the display good in the first place? How is that a valid review?

[–] [email protected] 4 points 4 days ago

Who knows? Maybe it just needs a big, big push, like Wayland.

[–] [email protected] 2 points 4 days ago

I’m happy to help! Good luck!

 

It's pages and pages of this. Maybe you want to restrict who can log in and create repositories.

 

I’m versed enough in SQL and RDBMS that I can put things in the third normal form with relative ease. But the meta seems to be NoSQL. Backends often don’t even provide a SQL interface.

So, as far as I know, NoSQL is essentially a collection of files, usually JSON, paired with some querying capacity.

  1. What problem is it trying to solve?
  2. What advantages over traditional RDBMS?
  3. Where are its weaknesses?
  4. Can I make queries with complex WHERE clauses?
view more: next ›