But it introduces an artificial difference between edges and corners. You'd get the same ability for corners if you did them after the edges.
The slightly counterintuitive “magic” is that you can trade a corner swap for an edge swap: for permutation parity, corners and edges are interchangeable.
I'm fine with permissions. Heck, it's what I already say.
Login, no, just no.
Login is ambiguous to begin with, is it the action or the user identifier?
Login as the process of logging in, the best interpretation, is still pretty limited: authentication is the validation of a much longer chain of events than that. It may start with login, but it lasts for as long as the service accepts to believe such principal is behind such actions.
Login as username is IMHO the most common use of the word, and most obviously the wrong one to mean authentication.
To make things me interesting, auth already means authentication to me. I accept it can lead to confusion and a better substitute would be welcome.
DoTT copy protection involved balancing the portable battery's chemicals. Copying a word or phrase feels off brand for a LucasArts game, that was more of a Sierra thing.
Which specific version do you distinctly remember?
The issue isn't the figure 50, it's the drawing pool.
Thread-initial description was 50% of the market, which is ambiguous. It could refer to either the market in sales, which indicates highest growth, or the market in userbase, which could be the layman's “common”.
FWIW I'm very sorry I put you through this. My comment was low value, posted during insomnia, I was very surprised by the reach it gained while I slept at last.
The point is, calling it zero-tolerance when it's not is misleading. There's a perfectly fine way to describe zero-tolerance with exceptions, and it's not even far fetched: “low tolerance”.
Complete sentences may make it possible to pretend bad wording is consistent, but that doesn't make it good wording.
The limit for a .COM's useful payload is 64KiB, but that wouldn't necessarily prevent the actual file from being bigger, with either truncate or wrapover semantics.
More generally, I'd be curious to know how they'd practically tune a keyboard to 12TET before the electronic chromatic tuner got around. Start with Pythagorean fifths then compress ever-so slightly? How'd you keep them… equal?
But it introduces an artificial difference between edges and corners. You'd get the same ability for corners if you did them after the edges.
The slightly counterintuitive “magic” is that you can trade a corner swap for an edge swap: for permutation parity, corners and edges are interchangeable.