News for hackers. Stuff that matters.
Re:IBM Completes Acquisition of HashiCorp by JohnMakin on Thursday February 27, 2025 @08:08PM (#43200472)
The same as in any other language when what you wrote was not what you intended? Sorry, I’m really confused what your complaint here is or how you’d prefer it to work. If you make a sensitive resource managed by any kind of IAC, of course the IAC can destroy it in a manner that would result in irretrievable data loss. The language has for forever put semantics in place to prevent that, and I’m not sure as a power user I’d want it any other way, I’m explicit with what I want it to do and dont want it making crazy assumptions that I didnt write.

like, what happens if you forget to free a pointer in c? sorry for snark but there are an unbelievably numerous amount of things to complain about in tf, never heard this one.

Re:IBM Completes Acquisition of HashiCorp by defrost on Thursday February 27, 2025 @08:17PM (#43200527)
> what happens if you forget to free a pointer in c?

Assuming you mean 'forget' to free malloc'd space referenced by at least one pointer, that's an easy one .. it's reclaimed by the OS when the process ends.

Whether that's a bad thing or not really depends on context - there are entire suites of interlocked processing pipelines built about the notion of allocating required resources, throughputing data, and terminating on completion - no free()'s

Re:IBM Completes Acquisition of HashiCorp by JohnMakin on Thursday February 27, 2025 @08:20PM (#43200543)
surely my salient point is recognized regardless of semantics, but thanks for the correction. To use another example in another post - what happens if you DROP TABLE in sql?
Re:IBM Completes Acquisition of HashiCorp by shermantanktop on Thursday February 27, 2025 @08:54PM (#43200780)
What happens is that you call Iron Mountain and find out that those tapes don't actually have anything useful on them.
Re:IBM Completes Acquisition of HashiCorp by fc417fc802 on Friday February 28, 2025 @03:17AM (#43203093)
DROP TABLE is explicit. Inadvertently removing a line from a config file and having Postgres decide to automatically "clean up" that "unneeded table" would be a more apt analogy.