Narwhalrus
I’ll have to give it another try.
I should clarify that the issues I had were podman compose being able to run unaltered compose files that worked with docker compose, many of which were fairly complicated. It may have been adequate for simpler use cases back when I tried it.
Some of the “misleading” statements were Harris neglecting to enumerate the reasons why a stated policy goal might not succeed, which would be incredibly unusual to include in a speech of this nature.
I guess the point the author was trying to make was that saying you “will” do something in office is a promise, and if you don’t have the ability to guarantee that promise can be kept you shouldn’t say that thing at all? I love me some NPR but they’re really bending over backwards with some of these…
Typically, I can read an “average” open source programmers code. One of the issues I have with C++ is the standard library source seems to be completely incomprehensible.
I recently started learning rust, and the idea of being able to look at the standard library source to understand something without having to travel through 10 layers of abstraction was incredible to me.
Agree with this. I think tactfully pointing out minor issues you see can be helpful because the implementor is closer to the problem and may have just overlooked the issue and can come up with a solution easily. I’ve been on the giving and receiving end of this, and so long as everyone is behaving professionally, it’s always been helpful.
On the “tactful” note, I’ll generally say something like: “I don’t have a solution, but I see problem. I don’t know that this is reason enough to hold up this PR. I’ll leave it up to you.”