Edge didn't have extensions when it first came out, but it does have them now, including: uBlock, Adblock, LastPass, RES, Tampermonkey. Still nowhere near what Firefox or Chrome has though.
Looking at 200 years as 20 generations ignores the fact that grandparents can speak directly to their grandchildren, or that people have children past 20 years of age. President John Tyler was in his mid 20s during the Battle of Waterloo, and his grandchildren are still alive - so only 2 generations removed from someone contemporary to that event.
"10 generations" is just a term meaning "a very long time". It doesn't mean that knowledge is transferred in 20-year lumps.
So, there's a great video on Youtube by a law professor entitled "Don't talk to cops", about the 5th amendment[1]. At the start of the talk, he tells the class to listen to a statement, and that there will be a simple test in a little while. Halfway through the talk, he asks a multi-choice question about the statement, and the class flubs it. He points out that they were in the comfortable, relaxed atmosphere of the classroom and were warned about it beforehand. If people mangle that kind of situation in only 20 minutes, what hope does a grandpappy-chain have?
Or a more real-world example: Australia's isolationist party (think UKIP, Trump) has about 8% of the vote and is led by Pauline Hanson. Hanson has waxed lyrical in the past about the golden years of Australia in her youth... which has been fact-checked, and the things she thinks were in early-70s Australia didn't happen until years later. She genuinely believes that all those years ago, society zigged when it actually zagged. This is in only one person's lifetime, sourcing her own experiences.
In short, no, a grandpappy-chain crossing 200 years is not sufficient for detail, especially when you're basing a moral code on the events and the semantics of the words matter. "My grandfather's grandfather fought at Waterloo and was a gunner" may survive, but "these are the political events leading up to Waterloo and the nuances they lend" isn't, nor is personal opinion or experience. How many of us have heard any detailed stories of our grandfather's grandfather's grandfather, let alone enough to write an epistle about it?
[1] https://www.youtube.com/watch?v=i8z7NC5sgik - it's an entertaining talk, and goes through a lot of the problems with memory and opinion. There's a second part as well, from a seasoned cop talking about his side of the equation.
When applying for insurance for our house built in the 1780's, my wife and I couldn't find a style/year combo that the online form would accept. We thought it was a Colonial, but maybe it is Georgian? The farmstead stabled the original Morgan horse sire, and is pictured on page 12 here: https://www.morganhorse.com/upload/photos/905TMH_Jan2015_Jus...
I have the Field Guide to American Houses. I'll take a look through it tonight and let you know, but given the era it's probably Georgian. It's not Federal, or Dutch/French/Spanish colonial. It might be what is considered a "folk" house, but those are generally what might be considered a shack.
I you type "Start-VM -name <TAB>", it won't list the list of the VMs, but rather the list of the files in the current directory. That's not exactly what I would call insightful.
I didn't know about the CTR+SPACE. That being said it doesn't seem much more insightful than TAB. And no description of what the argument does.
The issue with "Start-VM -name <TAB>" is not an issue with Powershell itself, but with the Start-VM cmdlet; the Start-VM cmdlet could have been designed to complete from the list of VMs.
I saw it as white and gold originally, but later when I looked at it I had scrolled down the page so that the top part of the picture was hidden, and I saw the dress as blue and black.
Now I see blue and black if I view the whole image or bottom 2/3rds of the image, and white and gold when viewing the top 1/3rd of the image.
I was going to note that 8pen[1] was left out of the Android list, but it doesn't appear to be on the Play Store right now. According to their website they are working on a new version.
No, that would work very similarly to the greedy version. The backtracking happens because the \d gets matched to the '1' and the whole thing has to be rolled back when the $ attempts match and instead finds '2' (this would happen again if there were more digits for \d to speculatively match on). So the backtracking is not caused by the laziness or greediness of the \D* ; we really do want to gobble up all of the non-digits.
On the two options generally:
/(\d)\D*$/
is problematic if you have a lot of digits, while
/.*(\d)/
is problematic if you have a lot of text after the last digit. Both could potentially be optimized by the engine to run right-to-left (the former because it's anchored to the end and the latter because it greedily matches to the beginning), and then both would do well. I'm not sure if that happens in practice.
Overall, I prefer the latter, both because I think it's clearer and because its perf characteristics hold up under a wider variety of inputs.
Edit: how do you make literal asterisks on HN without having a space after them?
Technically, while they both capture the same digit, the match itself it different, including either everything before that digit or everything after it. But I tend to liberally use lookaround to keep the actual match clean myself; maybe others go more often for a capturing group. (Well, and not being able to use arbitrary-length lookaround in most engines might be a reason too.)
