"potrzebie" was the default password for Wizard(#1) on TinyMUD and its derivatives. If I recall correctly, that usage is traced all the way back to Jim Aspnes' original, minimal database.
I don't remember whether it was Potrzebie or one of the other classic MAD nonsense words, but one day I was amazed to see it as a town name on a sign in the Czech Republic. With a couple of accents.
> This type of criticism reads to me as a general hatred of what humanity actually is.
No, that's really shallow. "Humanity" is a perennial struggle. If I'd be looking for a word for the lowest common denominator it would be "beastliness", to stay on topic of the thread.
That criticism reads to me as a general hatred of what beastliness actually is.
Had a math teach full of pithy, paradoxical, sardonic and witty quotes. Told us that if we only take away one from his class is that you can never go wrong attributing an unknown quote to Mark Twain or Benjamin Franklin.
It's a question of a typical behavior of mammoth. One method would work if an encircled mammoth was apt to charge humans. The other method would work if a mammoth was prone to panic and always ran away from aggressors. Looking however at the size of the animal, I doubt if the latter was its survival strategy.
German totalitarism did not cause Britain to go to war but it was why Britain did not negotiate peace in 1940.
German totalitarism was why they never held any serious legitimacy among conquered Poles and later Russians. Terror and more terror. It says something that, after long hesitation, Russians solidified around Stalin. Is it an anachronism as well? Did they see any hope for a prosperous post-war future with/under Hitler?
I'd like to suggest a minor improvement: Poles instead of being "no better than Nazis" as an entire nation, should become implicitly included in the "Nazis" in your future online work (on that specific account).
That's much more clarity of message, see? After all, your late grandfather wouldn't exactly disagree with that.
I can't ask him what he meant as he died almost 20 years ago, but I believe he was speaking emotionally as a reaction to being attacked as a kid as well as some neighbours helping the nazis by turning over some people from his family that were trying to hide. Of course the Nazis are to blame for the industrialised systematic murder they introduced to Europe (not only again Jews) and I never claimed Poland as a nation was as bad as the Third Reich was (and either way I don't condemn people for the sins of their ancestors, especially those that were done before they were even born).
There are some facts of note here, not only emotions. You saw the thing primarily through your grandfather's lens, or kinda reconciling it with the "other side" online (my guesswork), but I offer starkly different perspective.
1. There were times and nations where "anti-semitism, period" was a complete political program that won legal democratic elections.
2. In Poland this program was always in substantial minority, geography and economics nonwithstanding.
3. People susceptible to such programs are a part of the problem, not a part of the solution. The program is about labels, but it breeds the hate towards an actual neighbor. Even if the idea is changed to "it's all because of Zambians". Or Poles.
What? That's a weirdly money-minded question. I'm not gonna do some Google interview-esque estimation question to answer that, but I'll elaborate on how I use those features, because I enjoy discussing them.
I use line range history the most, multiple times per day, since it's a much better alternative to line blame in most situations. You get the full historical context of a line instead of just the last commit.
File blame is really useful when I'm encountering new code, and I want to quickly find out who has the most "responsibility" over it, oftentimes so I can go and ask them about it if I need more clarification.
File history is especially useful when I come back to a file that I originally wrote or was familiar with, some time has passed, and now I want to re-familiarize myself with all the changes since the last time I was familiar (could be years). Rename detection is useful when there are repository-wide restructures, which has happened a couple of time in the main repository I work on. Otherwise, your history will cut off at that refactor, which is really irritating.
I use path history like file history, but to re-familiarize myself with large modules (admittedly less often than file history, but it comes up).
I'm newer to pickaxe, but I've used it 2 or 3 times in the past year to track some chunks of code throughout a refactor. That's how a lot of these little tools that Git has work. You might only use them a few times per year, but when you need them, they're really amazing.
It seems like Jujutsu focuses a lot on the commit authoring and modification flows, and it looks like it offers improvements in those areas, but I don't see much functionality in the history investigation area. They might be considered niche features to some, but I think this functionality becomes more valuable the older and larger a codebase gets.
> The Object Management Group® Standards Development Organization (OMG® SDO) is a global, open membership, non-profit consortium.
reply