You've been able to turn off cookies since the beginning in any sort of competent browser.
707 karma · joined May 10, 2020
You've been able to turn off cookies since the beginning in any sort of competent browser.
But the point of the comment is the formal/common divide rather than the specific example.
For example, the formal definition of the Liskov Substitution Principal:
> Let ϕ(x) be a property provable about objects x of type T. Then ϕ(y) should be true for objects y of type S where S is a subtype of T.
This doesn't allow any change in behavior when subclassing. Not even the addition of logging, which makes the overriding of methods generally useless. Yet languages still provide this feature (perhaps to their detriment, but they still do).
There's also a common definition of the Liskov Substitution Principal:
> Functions that use pointers or references to base classes must be able to use objects of derived classes without knowing it.
This is, generally speaking, what people are talking about when the mention the Liskov Substitution Principal, unless they're actively writing an academic paper on the topic.
Bringing up the academic definition when someone is using the common definition is 1. not relevant and 2. usually not helpful.
If they use "agile" as a noun, they generally have no idea what they're talking about and you should be careful.
To extend your analogy, it's not Anheuser-Busch pissing off the brewers. It's Anheuser-Bush pissing off all the hops farmers.
Google's in the same position Microsoft was in the 00s. They don't make most of the stuff people actually want to use. You piss off the people making the stuff, eventually they start making stuff elsewhere.
It's a problem if you do drugs and are hiding it from someone (say, family). Then you can be blackmailed.
We don't need any of that, we just have to stop making fun of people who spell things phonetically.
[0] https://en.wikipedia.org/wiki/1978_California_Proposition_13
Rename across the project is introduced by lsps.
As for renaming, I don't use it particularly often, but it's documented in microsoft's code action documentation[0] to include: Extract method, Extract function, Extract variable, Extract interface from class (some of those might be language/server dependent).
The neovim framework[1] at least does provide a wrapper for the code action.
VSCode gets most of its capabilities outside text editing from language servers. So the rule of thumb is that if VSCode has it, vim/neovim/emacs usually have it these days.
[0] https://microsoft.github.io/language-server-protocol/specifi...
Admittedly, it's not a risk you want to take if you don't have to, but if you have no other option, it's workable.
The old unix editors have had rename across project, find references, go to definition/implementation for several years at this point via lsps (the same way vscode gets its functionality).
> What about integrated debugging
Those are usually (slightly ecosystem dependent) wrappers around a terminal debugger.
> What about hot reload?
Correct me if I'm wrong, but these are also wrappers around cli functionality (once again, might be ecosystem dependent). And you're probably just saving yourself the trouble of writing/running a script.
Seriously, lsps have gotten really good.
Ok, I'll bite. If it's the wrong emotions controlling you, what do you do then?
Please don't suggest any course of action that requires you to be in control.
You'd have to build your own infrastructure, but you could make an actual credit card. It would have to be super jank at first (you might even have to cut actual physical checks at first). Fundamentally, a credit card is just you paying for somebody's transactions, and billing them at the end of the month (and suing them if they don't pay up).
It would be slow, and the service would be horrible, but the people accepting your money don't have a ton of other options.
Here's an NPR article about a guy who has one: https://www.npr.org/2014/07/27/335839280/sold-harrier-jump-j...
Admittedly, I'm not sure what a supreme court does if they can't do that, but it's kinda funny that they bootstrapped it themselves.
Say, for example, spray painting something that would make a particular politician mad along a parade route that they're going to be taking.
It might be a non-central example, but I think it belongs in the category.
These two statements seem to be at odds. In order to know if we're improving, we have to know if the behavior is becoming more frequent or less.
Sure, but it can definitely break a tie. Frankly, operator overloading can create some really nice apis. And code that's pleasing to read takes less mental overhead to pick up.
Not really. Every government ultimately draws their legitimacy from the consent of the governed. If enough people riot and/or strike, you're done. Even Rome had a grain ration to keep the people content.
Your options for pressure usually come down to making the people of that country uncomfortable, or military action. Neither of which are very comfortable for those on the bottom.
You can also bribe the government to clean up their act, but that has a mixed record. I also wouldn't really call it putting pressure on the regime.
getattr(thing, u'attribute_with_unicode_characters')
This would work in both python 2.7 and 3.9 (probably works with other 3.X versions but it's the one I actually tried).
If I'm understanding your comment correctly this time, it would look something like:
getattr(thing, b'attribute_name')