> Come to think of it, if there is a latching door on the detergent tray, your dishwasher definitely has a prewash cycle, or else they’d skip the door entirely
Alec also mentions this briefly in the linked video; if manufacturers could avoid the cost of a latching mechanism, they absolutely would. Its presence means a pre-wash cycle exists.
My GE seems to skip the prewash cycle on the default setting for whatever reason. It does use a prewash on its "heavy duty" cycle though. Incidentally "heavy duty" also works infinitely better, with no more damage done to my dishes. YMMV of course.
Extreme aversion to NIH syndrome, perhaps? I agree that it's weird. Sure, don't try to roll your own crypto library but the amount of `require('left-pad')` in the wild is egregious.
Your argument highlights its own flaw; changing your editor opens up a world of tooling that's certainly adequate for most use cases you can throw at it, but it also requires either discarding or (worse) un-learning all of the tooling that you've learned for your current editor.
For example, I'm perfectly content to use nvim as my primary editor, and this was born out of having to develop for and administer literally tens of thousands of linux servers professionally. I have all the plug-ins and configuration necessary for productivity on my development machines, and when I'm on a remote system ad hoc editing a configuration it already has a built-in lightweight version of the editor I'm already used to.
If I switched to Emacs locally, I'd still have to maintain a working knowledge of vi and context switch when in a remote shell. Changing to Emacs would require more cognitive bandwidth when the whole purpose of "switching for org mode" is to reduce mental load.
> If I switched to Emacs locally, I'd still have to maintain a working knowledge of vi and context switch when in a remote shell.
Even ignoring the possibility of installing Emacs on remote systems, there are still alternatives:
1. You can run remote shells within Emacs, and edit files remotely using TRAMP. When you are editing a remote file, shell commands run from Emacs run on the remote system.
2. You could use Evil, the Emacs implementation of vim. Then you would use the same bindings everywhere.
3. I have been running Emacs locally for literal decades now, but I still remember and use vi frequently, both locally and remotely. It’s really not a problem.
I feel like there must be an editor version of the Blub Paradox.
Cooling, lubrication, debris removal and dust control. Mostly in that order.
But yeah, you're completely right about the chisel. Hammer and chisel is how we've processed rocks for most of history (all the way back to flint knapping).
Wet processing for tile/stone is really only about 100 years old, since we didn't have a usable cutting abrasive until diamond blades came around in the late 1800s.
---
All that aside, the problem with a hammer & chisel is that it's hard to be precise. It's not impossible, but it's definitely a skill requiring mastery.
If we expand the scope a little and include ceramics - then yes, we did need quite a bit of water.
Brick, Clay, Cement, etc - they were all good alternatives to chiseling stone to get a very hard, stone-like material in a very specific shape, and they all require good amounts of water.
>The models estimated that Oldowan stone tools originated 2.617-2.644 million years ago, 36,000 to 63,000 years earlier than current evidence. The Acheulean’s origin was pushed back further by at least 55,000 years to 1.815-1.823 million years ago.
These days, with high-power cutting tools also for cooling. If you have a 50 HP saw, that energy has to go somewhere, and it doesn't all go into the dust and get carried away. If carbide blades get too hot, the solder melts and the brazed inserts fall out, and for steel, carbide and diamonds, the hotter they get the softer they get and and the faster the tool wears.
And other than the cost of the tools, there is one thing harder to drill than a rock, and that's a rock with the previous drill bit's carbide insert stuck at the bottom of the hole!
I've built a setup that orchestrates updates for any number of remotes without needing a permanently hosted registry. I have a container build VM at HQ that also runs a registry container pointed at the local image store. Updates involve connecting to remote hosts over SSH, establishing a reverse tunnel, and triggering the remote hosts to pull from the "localhost" registry (over the tunnel to my buildserver registry).
The connection back to HQ only lasts as long as necessary to pull the layers, tagging works as expected, etc etc. It's like having an on-demand hosted registry and requires no additional cruft on the remotes. I've been migrating to Podman and this process works flawlessly there too, fwiw.
This obituary is so well written that it could be a front page star on HN. I am not joking. Incredible. You dad was the like the good guy version of the Terminator -- unstoppable in all forms.
Sorry for your loss. He saved so many lives, what an incredible legacy he left on the world. He deserves to be celebrated widely. Please make a Wikipedia entry for his accomplishments?
> he recalled that when starting his residency at the Children's Hospital in Philadelphia in 1970, the survival rate for the sick children was only 30 percent
Jesus, 30 percent survival rate of children. I couldn't image working in that kind of situation and not be emotionally destroyed.
> Going from a 30 percent to an 80 percent cure rate, I'd say we are getting there
Alec also mentions this briefly in the linked video; if manufacturers could avoid the cost of a latching mechanism, they absolutely would. Its presence means a pre-wash cycle exists.