rustyminnow

Indeed. In both this scenario and our modern one, we rely on the difficulty of "key material" reproduction being greater than the difficulty of its creation.

In the old days a king would "sign" his proclamations by pressing his "unforgeable" signet into a wax seal. This proved the authenticity of the proclamation.

Normally, the king would declare and sign a proc stating that anything signed by his secretary's "unforgeable" signet was to be respected as well. The secretary could delegate authority to others in turn.

Well turns out that one of the signets in the chain of trust was just a picture of a "four" that anybody could have forged, but nobody noticed because in all of the ceremony and stacks of parchment with wax seals, nobody actually checked if the signet was secure.

OP version is also buggier, laggier, and harder to use. OP's might be flashier with fancy low-poly models, but this one is in much better taste as an actual guide.

Sometimes. When my manager went on sabbatical I had to reach out directly to other teams. We got so much done with that higher bandwidth, unmediated communication. OTOH my boss's boss was constantly breathing down my neck for status updates. There's a balance to everything I suppose.

My great-grandfather - a carpenter in the 1930s - apparently had a saying: "If a man can make it, a man can fix it."

While /technically/ still true, I lament that it is increasingly inapplicable to the world around us today.

Is it that simple though? There could be so many other reasons. Maybe the particular issue is related to a specific hardware or network configuration that the developers have never run into or can't reproduce.

Linux needs polish for sure, but given a finite amount of time, energy, and money the reasons are likely more complicated than "they don't care"

I agree about system design, but I think - especially in the context of your networking example - the complexity lives below the OS and not a case where it's a lack of effort.

Networking protocols, connections, error states, etc are inherently complex and require equally sophisticated handling that linux may not always do. Some software chooses not to handle at all and expose directly to the user - but others like KDE simply lack the millions of dev-hours of polish that Windows and Mac have.

I also like old carburetors and simple electronics, but we're in the vast, vast minority. Most people want a car they don't have to think about or understand, looks pretty, and will take it to a shop when something goes wrong.

ag is also a little more ergonomic with its default flex casing: your query is case-sensitive if it has any uppercase letters, otherwise case-INsensitive. rg defaults to case-sensitive (but does have flags for insensitive and flex casing)

I asked my AI for a rebuttal to your argument and it came up with some pretty good points.

Since inputs are more interesting than outputs I've included my prompt; you should submit it to your AI to see why you're wrong.

> I'm debating with someone online. Can you come up with a counter argument? Here's what they said: <QUOTE>

I don't see this mentioned enough! Wood glue will improve the stability massively.

Obviously beds and huge bookshelves might need to come apart again, so use your best judgement. But chairs, dressers, end-tables, etc. are completely worth it.

I've started wood-gluing together my IKEA and other flat-pack furniture to try and increase its usable life since - as you said - it's counterproductive to dis/re-assemble most of it anyways. I've not been at it long enough to claim effectiveness, but so far nothing has started to wobble.