I mean, that isolated example doesn't really demonstrate the benefit of a walrus operator does it? You could have just written "if re.match(x, y): do_something()". If you re-used the result of computation within the if statement, I feel that would be a better example, eg. "m = re.match(x, y); if m: do_something(m)".
I mean, that does seem like the optimal outcome, doesn't it? Not only is Nike not using sweatshop labor, but all their competitors are also not using sweatshop labor. Did you want Nike to stop just because they felt bad, but their competitors could continue to use sweatshop labor? As you point out, that would mean that they would be pushed out of the market and we'd just have a new major corporation using sweatshop labor to be mad at.
I am an example which supports this notion. I've done some Python programming about 10 years ago but then took a break from programming altogether for the last 9 years. Last year I got back into it and have been using Python 3.7, and I personally love all the most recent stuff. I hate having to go back to 3.5 or even 3.6, and I end up pulling in stuff from futures.
To be fair, Guido stepped down because of the way the community reacted.
"The straw that broke the camel’s back was a very contentious Python enhancement proposal, where after I had accepted it, people went to social media like Twitter and said things that really hurt me personally. And some of the people who said hurtful things were actually core Python developers, so I felt that I didn’t quite have the trust of the Python core developer team anymore."
The Nike sweatshop situation is actually a counterexample to your point. People complained and, at least according to what I read, not only did Nike change but they lobbied for legislation to force their competitors to change as well.
If you're charging $80/hour but then work more hours than you charge your effective hourly wage is less than $80/hour. This is an incredibly low wage (less than half) for typical web design work in my area (New England).
It's clearly always possible to detect whether an ad was seen. Often, the content owners do not bother putting such measures in place, but the advertisers definitely do. (It's even easier from their perspective to check if the ad has been served or not, as many ad blockers prevent the ad from even downloading by sending all requests to that domain into a black hole and so the ad is never even requested from the server.)
Presumably if the expected number of bikes it contains is greater than N, where N is some number between 0 and 10 decided on by someone in control of such infrastructure.
I just found this channel and I'm amazed at how technical and well researched everything is: Tech Ingredients
The best thing is that he repeats experiments to verify the concepts he is exploring. It seems to still be in its infancy, it could benefit from practical improvements, such as including links to parts, as well as professional video editing, but the content is really strong.
So, to be clear, you don't like it when projects choose to use their preferred language, and so you will search for a project which uses your preferred language?
How do avoid the incentive of sites who pad their content in ways to make you spend longer on the site? Ideally the market would take care of this, where people would be more likely to visit articles which were more concise because they were more useful, but longer content also is generally a positive metric for search results and I feel like we often fall into this local sub-optimum.
I agree to some extent, however most people I have seen with password books still have very simple passwords and often reuse them or create them with simple rules (pet's name + year born + first three characters of the site I'm logging into).
Did you try contacting customer service? I'd bet dollars to donuts that you get a full refund, no need to even return it. The Google-esque experience you described only occurs if there's no customer service to even contact, Amazon's customer service is very easy to contact.
It seems like you are missing the original point. People aren't working around bugs in Chromium, they are (either inadvertently or intentionally) developing apps which rely on the buggy functionality.
Tires, oil, brakes, belts, wheel bearings, transmission... With a mechanical system like a car there are lots of things which wear down with use.
Instead of trying to figure out the actual difference yourself, you can simply look at what people are willing to pay for a car which is the same year but has different amounts of mileage. The literal resale value of your car changes drastically depending on mileage, that is the actual unrealized cost most of these ride sharing services exploit.
Not sure I understand your math here. A car depreciates faster if it is driven (more repairs, needs to be replaced sooner). Just because I already own a car doesn't mean it's only the cost of fuel to drive it.