I feel like this has been missing in more recent videos though.
84 karma · joined March 8, 2016
I feel like this has been missing in more recent videos though.
On Linux, when I force Chrome to use sRGB (chrome://flags/#force-color-profile) it makes the colors identical to Firefox's. It doesn't seem to make a difference on MacOS though, the colors are always identical there
Wait, what. Don't basically all browsers nowadays keep previous pages in memory exactly not to do this?
[1] https://nodejs.org/api/worker_threads.html#worker_threads_po...
Routing is required, but generally the rules allow things to be "reasonable" and "acceptable", which lets all these weird implementations through.
Honestly, they should remove the "Implementation approach" column, because basically every implementation is marked as "realistic", making it meaningless.
> Any error system that relies upon developer discipline will fail because errors will be missed.
> Any error system that handles all errors the same way will fail because there are some errors we can ignore, and some errors we must not ignore.
Not sure how that's true for Rust. Functions that can fail, return a Result, that contains either a value or an error. If you want to use the value, you have to either explicitly check which one is it (you can handle or ignore the error at this point), or quickly access it by unwrapping the Result, which will crash (panic) the program on error.