That's the ideal, but unfortunately not always an option when you're on the receiving end. We're building a data cleaning tool, so the whole point is dealing with messy user-uploaded CSVs where we don't control the export format. If we could mandate ISO 8601 everywhere, life would be much simpler. But the reality is people copy-paste from Excel, export from legacy systems, or hand-edit CSVs, and we need to handle what shows up.
I wouldn't compare an public counsel of an lawyer with ai pretending doing the same.
If the lawyer gave bad advice, they would have been responsible.
if "AI" says there was an precent in case xyz, OpenAI, Perplexity, xai, ... will say: it was the responsiblity of the person using the tool.
I would guess its because it is an vital system. Initrd depends on it, a lot of paths are backed by tmpfs, ...
An error in that subsystem could make it unbootable
At an previous employer i was able to cut down on the needed space by standartising the layers and adding a timelimit in which the tags were available. The base images were build after we rolled out updates of packages and "encouraged" everyone to use those for their containers. These containers were also minified as much as needed(deduplicated files, removing useless stuff, ...), without sacrificing usability. I also used buildah to combine everything into an single layer to prevent removed files from wasting space. Sadly DNF blows up the images so it was hard to minify it much.
reply