hhda

We assume we know the possible space for YouTube URLs, but it might not be a fair assumption.

Take phone numbers as an analogy. Without foreknowledge or without careful analysis of the distribution of phone numbers, you might assume all numbers are valid, but in fact 555-xxxx is always invalid within each area code [0]. For each set of reserved numbers our address space is that much smaller, which can skew the results of the statistics we gather from it if we don't exclude them from our original calculations.

It may be that YouTube reserves off certain address spaces (eg maybe it can't start with a 0, or maybe two visually similar values cannot be next to each other (eg I and 1), etc), which may make this sampling method (slightly less) accurate than it might otherwise appear.

[0] https://en.wikipedia.org/wiki/555_(telephone_number)

Thanks, I didn't know about `-t`, I'll read up on it.

Yeah, the -M command is wonderful (super handy for ignoring minified files that you don't want to see results from, etc), and also great is the -g command (eg `-g *.cs` and you'll just search in files that have the .cs extension).

Also the fact that it is a standalone portable executable can be super handy. Often when working on a new machine, I'll drop in the executable and an alias for grep that points to rg, so if muscle memory kicks in and I type grep it will still use rg.

For that, I believe you need to use cargo-geiger[0] and audit the results.

[0] - https://github.com/rust-secure-code/cargo-geiger

You can add `#![forbid(unsafe_code)]` to your codebase to avoid any unsafe Rust, which should prevent buffer overflows. Obviously it may make writing a codebase somewhat harder.

From what I can tell, yearly Search ad revenue is in the neighborhood of $104 billion [0], and the number of yearly searches served by Google is somewhere in the neighborhood of 3.1 trillion [1]. This brings the revenue per search to somewhere between 3 and 3.5 cents.

[0] https://abc.xyz/investor/static/pdf/20210203_alphabet_10K.pd... (page 33)

[1] https://www.oberlo.com/blog/google-search-statistics

I guess the issue is that you assumed the type of egg and jumped to a conclusion about the egg you assumed was used in the experiment. You also assumed the environment - who is to say that the environment is earth? Etc etc.

The problem isn't with mathematicians.

I always find the postmortem of a major tech outage interesting. Ever since Google had a major outage with Maps, etc, I've been going back[0] to check for their breakdown of why they had the outage. Both the technical reason and the way it is explained is always something I'm interested in - like getting a peek behind the curtain, without a chance to see any details.

[0] https://status.cloud.google.com/maps-platform/incidents/8yNk...

Laravel 9 was released today (hence this thread) - Laravel 8 is the major version that came out directly before Laravel 9. Further, Laravel 9 is essentially Laravel 8 with a bump to the dependencies, with most higher impact changes coming as a result of those dependencies being updated[1]. The Laravel 8 From Scratch series has videos as recently as August[2], with the What's New in Laravel 9 series already having 11 videos[3], with the most recent posted yesterday. The Laracasts video series are still very much actively updated (with Jeffrey, who runs it adding new teachers in the last year).

And Laracasts is a 3rd party learning resource anyway, with the first party docs all being well maintained.

1. https://laravel.com/docs/9.x/upgrade

2. https://laracasts.com/series/laravel-8-from-scratch/episodes...

3. https://laracasts.com/series/whats-new-in-laravel-9