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.

>> 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.

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.

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

I.e. specifically regex, which is highly relevant in searching through strings: https://github.com/mariomka/regex-benchmark

And the always interesting techempower Project, which leaves the implementation to participants of each round. https://www.techempower.com/benchmarks/#section=data-r21&tes...

Choose whatever category you wish there, js is faster then go in almost all categories there.

Even though I said it before, I'm going to repeat myself as I expect you to ignore my previous message: the language doesn't make any implementation fast or slow. You can have a well performing search engine in go and JS. The performance difference will most likely not be caused by the language with these two choices. And the same will apply with C/Rust. The language won't make the engine performant and creating a maximally performant search engine is hard. But a theoretically perfect implementation would likely be fastest in C/Rust, followed by the usual suspects such as Go/Java/C#/JS and finally ending with all other interpreted languages such as ruby and python

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.

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

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.

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.

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".

That's one step forward and about 30 steps backwards if you're actually doing that for security. Proxies silently accept broken TLS configuration all the time and serve then to you as https secured. You're unlikely to encounter invalid https configurations nowadays, so you likely won't ever notice, but it's definitely less secure to break the TLS connection in the proxy

A lot of them will be doing that, yes. They're teenagers until their 20th birthday, and a lot of people start to work between 16 and 20. In Germany, all of them will be paying a lot of their paycheck for the current pensioners.

It's called a generational contract here, and it boils down to current workers paying the current pensions - so when theyre ready for theirs, it will be the responsibility of that workforce to shoulder that burden.

This will fail within the next 20-30 years, realistically speaking and arguably already failed, as current pensioners are often extremely poor.

The parent comment was spot on with their comment wrt Germany, which was the context they explicitly set

I agree that these numbers always sound outlandish (I'm from Germany too), but they do seem to be true. Do keep in mind that while the wage gap is bad here, its several times worse in the USA.

It's just that it's impossible to scale that approach, so the larger the enterprise gets, the less you'll actually be shipping... As pretty much all of them seem to think it's easy to scale development teams, increasing their headcount and running productivity against a wall.

A small team has barely any space for Juniors however, so I think it's very good that both approaches exist in the wild

Surely you'd agree that this behavior (disabling exit until payment) is malicious in this context...

Applying that to this scenario: evading/postponing arrest after the cops started to look into you is luck, never giving them reason to look for/into you is what could be considered skill.

Or even more specific: it became luck as soon as it became clear that there was an admin. A lot of criminals that get caught want to be notorious however and build their "street creds".

With companies it just ends there and then