fyjvd90

4 ms·

1.
by fyjvd90 8y ago
I’m just taking the article at face value, they use the word container and say they’re not compatible. So maybe the article could be better, not sure.
2.
by fyjvd90 8y ago
I don’t think you’re reading the article, it says: > Each project has a separate internal representation of a container that is not shared. Because of this you cannot see Podman containers from within Buildah or vice versa. > Mounts a
3.
by fyjvd90 8y ago
See the table of the subtle differences, why does podman create images that aren’t compatible for example? Regardless of what Docker does, if you make tools that are for a specific use case why blur the lines?
4.
by fyjvd90 8y ago
I think that explanation is a little clearer, however the repos and the article don’t make this clear and the fact that podman also builds images makes it less crisp. > Some of the commands between the two projects overlap significantly
5.
by fyjvd90 8y ago
I may not fully understand what the tools can do but it seems overly narrow scoped. Also in that Unix philosophy you don’t duplicate functionality that’s slightly incompatible between tools to the point you need paragraphs and tables to exp
6.
by fyjvd90 8y ago
In that it adds complexity to have two tools vs one. And in the wild will add risk of mistakes and wasted time due mixups since they overlap and have incompatibilities. I’d rather give a team one tool, the only reason this is two tools is b
7.
by fyjvd90 8y ago
The more seasoned the manager or exec will say at this point that you should always see everyone as having good intentions. It’s of course not true at all, but seems to be one if the mental tools they use to not acknowledge what someone is
8.
by fyjvd90 8y ago
It’s also interesting how a democratic Rome voted for becoming an oligarchy.
9.
by fyjvd90 8y ago
Yeah PCI or FedRAMP have this 10 char password requirement, which of course no one can remember a 10 char password. So companies just make the password a pattern with some variations, effectively reducing the complexity to a tenth of a rand
10.
by fyjvd90 8y ago
It does, but there’s also what I call stupid security that doesn’t really add any measurable improvement, but does decrease productivity. Users out smart these systems all the time (e.g. forced password changes where you can’t use the last
11.
by fyjvd90 8y ago
Not Linux specific but: Don’t make your security encourage legitimate users to work around it due to pointless friction
12.
by fyjvd90 8y ago
OAuth is going to be hard to use if you don’t create an account though, there’s no way for DS to know what scopes to restrict the user to, it sounds like that was the core issue that broke their workflow.
13.
by fyjvd90 8y ago
I would also like to know why it takes my HMO (Kaiser) 6 weeks to make lenses, and why their invoices don’t list what products they sold you.
14.
by fyjvd90 8y ago
The argument isn’t correct, what does a user do when the download is damaged by an injection? A re-download results in exactly the same tampered with file.
15.
by fyjvd90 8y ago
Likewise, integrity of the download is the primary reason I’ve switched downloads to HTTPS too. The argument that singed downloads is enough fails to address what the user is supposed to do after the integrity has failed? A redownload can r
16.
by fyjvd90 8y ago
It also helps with integrity of the download.