For my own Rust project I require myself to have a comment for every unwrap call that explains why that unwrap will never panic. For everything else I let the function return an error, with help of the anyhow crate and error contexts.

Be careful, the actual logging can happen at a later time, and because the log function may take a reference to the value, if you modify r it may show the modified version of r in the logging instead of the original r.

Using -F with tail is even better than -f because it handles files getting truncated or getting created.

Exactly! This is why the server should just send a clear error message. 99% of the time the client just wants to show the error message to the end user, and not have to wrangle all kinds of normalized data into one.

This looks so over-engineered. Most of the time you only need an error message. Make the message clear enough so that it can be shown to the end user.

Everyone in this thread: PHP sucks because it was bad when I last used it 20 years ago.

Those haven’t existed in PHP anymore for a very long time.

Well better late than never.

It’s fine, we all know what you meant.

Actually it’s [object Object]

My RTX 2080 works perfectly fine with nvidia’s drivers on x11.

This is also how it is defined in the JSON Merge Patch RFC.

Reject kubernetes, join the Juju cluster.

We have “save your wallet hundreds of thousands by not automatically spinning up a crapton of resources if your app does an oopsie”! And we have “simply run on any public cloud or in your own datacenter with MAAS or locally with LXD”!

Nice troll