eb
TheSilentDrifter
eb7246eb8e26b0c48dd4f9c2a822a0f4d5c84138937195090932b61a2d756051

An ostrich with their head in the sand. Someone who has truly become a burden on society. A true shame. An embarrassment to the term jackass.

Honestly, yes. If the code fixes a problem, it doesn't matter its origins. I believe wholely in meritocracy. Anything else introduces bias.

Using `.unwrap()` is not "bad," per se. It is just frequently misused. Utilizing something like `match` or `if let` provides a more idomatic way of handling both expected and unexpected error-cases without causing your application to come to a grinding halt. One such example includes needing it to exit, but wanting to clean up artifacts. Another is creating and handling abstracted error types. Regardless, a good rule of thumb is only to use `.unwrap()` when you anticipate the desired failure outcome should be a panic.

If your Rust application is slow, you aren't writing or compiling it correctly, and that is the hard truth.

Why? The internal construction would be abysmal to set up... How will you handle insulation or HVAC? It is cool in theory, but the long-term ramifications would be very costly.

My school teacher telling me not to worry about learning about how budgets work because that is what you hire accountants are for... 🤦🏻‍♂️

Gimp, Krita, dark table, and inkscape are my go-to choices. Anything in particular you need to do?