It seems to me that as long as advertisers have ingenuity they will find new privacy harming ways of tracking us -- it seems like Goggle is moving earth to use their ingenuity instead to make a tracking device that isn't 'too identifying,' and could reasonably form the basis of a 'truce' between users and advertisers -- maybe we should let them?
NPVIC is state level-electoral meddling exactly on a par with what 45 tried in Michigan and Georgia, and aiming for the same outcome. The democrats pushing for it are not trying to correct some abstract statistical imbalance or make it easier for third party candidates to get seats: they are trying to swing elections in those states democratic, pure and simple.
I think that life would be better if employers honoured their wage obligations instead of drawing up elaborate networks of hidden fees and transfers which put employees' hard earned wages back into the employer's pocket. Nobody really owns anything, they have everything they think they earned on layaway.
> I'm a user not in the US or China, I don't want either the US or the CCP to be able to abuse/spy on me. But it's insane for US to claim the moral high ground when the legal barrier to the government using private data is literally just they have to pay a private company to do it [1].
Ah liberals, the undisputed champions of whataboutism.
We need to enforce the laws as they are written and right now that means prosecuting time theft by employees a criminal offense. Law and economics tells us that the degree of wrong done by inconveniencing someone is in proportion to the worth of that persons time. If a person of importance to society has a suit against them it must be speedily dismissed.
Calling skeptics as "denialists" is a rejection of scientific discourse. The skeptic could reasonably be defined as someone who doubts a proposition and gives reasons for doubting it: if truth is given as a condition of skepticism, it preempts the frame of discussion in which truths are settled, and makes discourse into a game of who can define the other out of existence more effectively.
I had a geocities website with homemade software. Yahoo removed it before it could enter the archive. It had a page with JavaScript that displayed modal dialog boxes repeatedly in a loop; Yahoo identified this JavaScript as a virus.
There's also the probably underappreciated packages ref-tf and ref-fd which let you write code that is polymorphic over the type of state reference. These can make 'ST' more acceptable because you don't have to make the decision of what state reference to use up front.
No that's not it, Randall is gesturing at utility theory -- the password is to something indifferent, so the person would decide that's it's not worth being beaten over (with the wrench) over. He's implying that the stuff being protected isn't that important.
It makes sense to me. Users lend social networks information they may prefer to keep private, and social networks make risky bets that third parties will not misuse this information. And they do so without informing the users themselves (except in the tos, but who reads that?). Why not regulate this?
A predicate is a computer program that accepts an input and returns "yes/no." A type system could be an arbitrary predicate which returns "well typed/not well typed" when given a term. But obviously there must be some difference between types and predicates, such as extensionality -- the type of an expression can be decided by examining the code alone.
Functions (or closures) are the prototypical codata... a co-inductive codata can be presented as a function space from an inductive datatype into some other type. It has a coinduction principle, derived from the induction principle of the parameter type. Traditional imperative code can be represented through the use of a free monad over a functor representing some command language, and the free monad is a codata as well.
Let me guess task manager could have managed the tasks better, i would have let it slide but if you call your program "task manager" in for a penny in for a pound.
The implementation of stdlib necessarily contains code which invokes implementation defined behavior, and the reason that the compiler implementation doesn't treat it in like manner is simply that it doesn't identify it as such or is prevented from doing so. So the treatment of libraries doesn't need to be consistent with that of user programs. Practices that ensure that such code is not optimized away include scattering the information needed to do so across multiple translation units, so that the compiler does not put them together.
This sort of thing is endemic to computing culture. Somebody says that a design is too inefficient or poorly thought out, then a practitioner comes along and crows, of course it works, all we had to do was overdesign it by a factor of ten.