y4mi

as the beginning of the article says: it all depends on what qualifies as a book

if you're including epub novels, that have never had a print done... then yeah, at least is gonna be the operating word, likely multiple times considering just how many fiction books are being produced on webnovel sites and then published as epubs for their fans to buy and support the author.

> Methods: git merge --ff-only or git rebase && git merge (extreme clean freaks add the --squash option)

>> Pros: Linear history, git log is easy to read, git revert requires no thought.

Does it require no thought because it's fundamentally impossible? if you're doing -ff without squashing it's gonna get hard to figure out which commits you'll have to revert I think. All histories get merged into a single stream after all.

> totally unfounded guess: that's how Google does it

I'm pretty sure Google doesn't do that. At least not as the primary information source.

I don't work for Google, so I could be mistaken, but I've provided several information updates before. Google gave me the "local guide" after my first accepted update and gave me gamified incentives to update and verify local information about businesses afterwards until I disabled them again. (Like notifications when I'm at a store to verify if there is a parking lot and things regarding to disabilities etc).

The questions are usually really innocuous and quick to answer, which pretty much makes the player into free labor for Google, one minute at a time.

I was required to provide some proof on some information like opening times and that's probably how they're linking back to the official website. But it happens through user input not automated scraping i believe.

I sometimes wish companies were required to report their opening hours when registering and the state made this information available through a public api.

It's not really possible as not all place have scheduled opening and closing times... But a dude can dream, right?

> C/Rust/Go version

Minor nitpick: JS/V8 beats Go in most benchmarks that are relevant for search.

JS is the outlier here however, because of the insane amount of optimizations that made it perform so unreasonably well, despite being an interpreted language.

It's usually only a "beautiful extendable maintainable paragon of elegance and purity" in the eyes of the original architect. Everyone else sees it as leaking abstraction with bolts everywhere to keep the original idea somewhat working... Or just a massive pile of technical debt.

Code quantity is always dependent on how well the person making this judgment understands the software. While I'm sure that everyone will agree that there are some clearly better ways of doing things, they sure as hell won't all agree on what these clearly better ways are.

One person's pile of garbage is the next person's perfect implementation with easy to understand procedural logic.

Please take note that I'm explicitly not saying that any implementation is better then another. I'm just trying to convey that the term technical debt very much depends on the mindset of the person looking at the implementation

Also "knowing" and actually knowing are different things.

There had been research done as far back as that which came to the conclusion that it causes climate change. But that doesn't mean that the governing body at that time was aware of the research and if so, really believed it or just thought that the researchers are massively exaggerating.

I know that the research was done on the behalf of the government, but that doesn't mean that everyone governing/deciding on these issues had access to/were aware of the results.

Aren't card PINs only 4 numbers long? That's almost 10k possible combinations I believe, pretty trivial to put together.

Checking which corresponds to what card is the hard step because you need access to an acquirer to my knowledge, and you'll lose that access quiet quickly if you attempt too many incorrect combinations.

Because i struggled to understand what you meant I'd like to rephrase it:

It matches only if the regex is applied to a singular word. It's not going to match if there is a sentence or any apostrophe etc, which is implied to be valid input because it supposedly matches "all words".

Please don't advocate for violence, even if it's only in jest.