Protesting that workers aren't getting paid by withholding money from workers is a rationalization. In the best outcome, the customer would be paying exactly the same amount that they pay now, or more, it just wouldn't be separated or optional in the bill.
You can tell whether people complain about tipping because of fairness or just because they want a discount by whether they also complain about mandatory, fixed percentage tipping, which is really just a service fee under another name.
> In the best outcome, the customer would be paying exactly the same amount that they pay now, or more, it just wouldn't be separated or optional in the bill.
I'd pay a premium just to avoid the distasteful master-servant relationship. It's insulting to assume that the customer would enjoy lording over others.
> just because they want a discount
It never crossed my mind that people do this. That's lousy.
I have no qualms paying whatever a vendor wants to label or however they want to itemize the receipt as long as the total number I owe is conveyed to me when I request to purchase something.
Also, a customer does not owe workers anything in the USA. Employers owe workers.
next they'll try to end the practice of wage labor by not paying their employees
if that's the goal it needs to be a systemic solution, which generally means or legislation, company policy, or worker organizing. otherwise you're just going around hurting people. if you don't want to tip service workers, stay home, and don't order delivery.
remember, that scene in Reservoir Dogs was intended to demonstrate that Mr Pink is a shortsighted asshole.
The first append version will more often be in a loop. It's unlikely that someone will know enough to use comprehensions but not enough to still use append.
This is a scoping rule, not typing. Scoping is a mechanism of symbol resolution, i.e. what do you mean by `foo` at line N. Is it a local, an argument, a global, or addresses a symbol defined in an enclosing scope? Most languages use explicit local definitions, searching implicit ones in outer scopes bottom-up, ending at the global scope. Python was the first popular non-basic language which made implicit assignments to be local and shadowing and function-scoped:
global x = 1
def setx():
if True:
x = 2 # completely different x
print x # prints 2, visible outside of `if`
setx()
print x # prints 1
This led to a funny keyword 'nonlocal', because you can't simply ignore scoping and pretend that you're BASIC in any serious program.
(To my opinion, python had a good start, but lost in the woods for no clear reason. It's a movie mutant of a language, which tried to appeal to non-programmers and somehow succeed, and then realized that non-programmers eventually become ones, and it's not hard. Now it's too late to fix this mess. End of opinion.)
Uh? Perl optionally requires you to declare variables, which is a good idea IMHO, no noise for small script and any experimented Perl programmer will have learned that 'use strict' is a really good idea for big scripts..
It would be impossible in any language that requires either explicit typing or some kind of 'let' keyword. (Or, in the fringe case, a language like Go which uses a different operator for initialisation-plus-assignment.)
Exactly. That's why I asked about languages that don't require explicit typing. My point is that it's a feature of many languages rather than a Python idiosyncrasy.
Declaration and explicit typing are logically orthogonal, but few if any languages require typing but not declaration. Lots require declaration but not typing.
Aren't NFTs essentially just file hashes/signatures that can be associated with a public/private key pair on a blockchain? If so, the link between the NFT and the key pair might be solid (as in cryptographically secure) but the link between the NFT and its "underlying asset" (which might be copyrightable) seems flimsy.
That being said, since both NFT ownership and our legal systems rely on consensus and majority opinion, it's not hard to imagine a corrupt society in which the opinion of judges is disregarded in favor of blockchain consensus.
Edit: you might be joking but it's an interesting question nonetheless because it highlights how various systems compete for legitimacy :)
I don't think you are missing anything. It is far more attractive on mobile due the the extension support and hence ad-blockers. That alone makes up for any (small) performance difference Firefox has.
Chrome on mobile without uBlock is as bad as you would expect.
It's not 2008 anymore, there are choices beyond Chrome and Firefox.
Kiwi and Brave are both Chromium based, and on mobile both are faster/less jittery than Firefox. Especially on web apps that have some level of interactivity with CSS transitions and transforms.
Kiwi has excellent support for Chrome extensions including UBO, and Brave comes with adblocking built in. Samsung Browser has adblocking as well.
And those choices are literally rebranded Chrome - which means they're likely going to be victims of Chrome Extension Manifest V3 nerfing content blockers in various ways (especially once Chrome fully sunsets MV2), no?
No, V2 is being kept internally and exposed for Enterprise Chrome deployments. We at Brave have committed to keeping webRequest exposed to extensions too, while the underlying support remains and can be enabled for all Brave users.