Happy to have spiders in my home until I find one in the shower with me. They don't understand how dangerous the shower is for them; I've lost too many good spiders to drowning.
Give it at least 9 minutes on broil in your oven.
Wow it looks like the hammer was going faster when it hit him than when it hit the ground. He might've been better off having the hammer dropped onto his face from the same height.
I currently have more audio issues on my MacBook Pro than my Linux desktop. The Mac will sometimes just fail to recognize headphones plugged into the 3.5mm TRS port. NixOS desktop w/ pipewire has no audio problems whatsoever.
I recently attended a Beyblade birthday party and it was rad.
Except the vast majority of the kernel is in driver modules.
So for an individual machine, the attack surface is not really any bigger than it needs to be.
The OS will only load modules it needs for your hardware, so the "bloat" only exists at the source code and binary size level. You are free to compile an optimized binary for your hardware. The complete kernel binary should fit in a 200MB boot partition.
As for maintenance, that's a fair point, but the effort is at least somewhat distributed if hardware devs provide the drivers.
You're kidding yourself. The norm in American bars is to have two urinals whose porcelain touches, and everyone pees with their buddy while having a boisterous chat.
Of all the stuff I've seen in the comments, this is actually feasible today.
This does seem like a potential issue if the PR is itself implementing more than one vertical slice of a feature. Then it could have been smaller and there might be wasted effort.
If the patches are small and well-organized then this isn't necessarily a bad thing. It will take more than one day to review it, but it clearly took much more time to write it.
"how to write sloppy rust code and squander most of the advantages of the language"
Only half serious. But I think really the only point that I agree with is taking the easy way out with the borrow checker. I mean, at least try to borrow when it's idiomatic, but if you get frustrated, clone (or move) instead.
Error handling when done well is not much harder than unwrapping everything, and you get many advantages. Learn to use thiserror for your library crates and anyhow for executables.
I also agree that you should avoid unsafe 99% of the time. If you think you need it, you probably don't.
Don't forget about lsd
tatterdemalion
0 post score0 comment score
The difference is that JS code served by a web server can change at the server's whim, and there is no standard way to verify that it matches what you expect except by reading it every time you visit the page.
With an extension, assuming you trust the browser itself, you can check that the extension matches its source, and you only need to do that once per install.