JWBananas

It can be a big issue. The newest release offers some improvements.

https://devblogs.microsoft.com/commandline/windows-subsystem-for-linux-september-2023-update/

Too soon

The phrase that immediately comes to mind is "poner la mesa." It translates from Spanish as "to set the table" but literally means "to put the table." Similarly, one might take photos with a camera, but the literal meaning of the Spanish phrase "sacar photos" is "to remove photos."

Linguistically and colloquially (the latter lending more to your example of adding cheese to something), we often use weird verbs in specific contexts.

What you've described might not fall into the category of proper grammar, but it also doesn't come across as strange or unexpected.

There are also unspoken rules about the ordering of adjectives to ~~blindly follow~~ follow blindly.

Edit to add: Proper, verbose grammar is also not usually necessary or even useful in the context of directions/commands, particularly in lists of such. Sure, "add cheese" would probably make a technical writer happier, but the point still gets across.

The context is important as well:

"What toppings do you put on your burgers?"

"I put cheese."

So, Rick, basically.

Liking Rick and Morty is not a personality type.

Wait...

The less said about Captain Picard and Doctor Crusher's child, the better.

Because if it ain't broke, you're not supposed to take it apart and fix it.

You can buy Ernest a coffee. That will certainly help keep the lights on. But you should probably take a look at the recent posts on his profile.

In addition to the personal issues, he hasn't been able to meet milestones. He gets sponsored by the same group as Lemmy's developers, and if he isn't reaching milestones, he isn't getting paid. And it sounds like his savings is running out.

While money certainly helps, it sounds like it's only the tip of the iceberg. Short of sponsoring a personal assistant and a project manager, I'm not really sure how we can help.

Some people don't think their thoughts are good enough to warrant their own post. But they might be more receptive to making a comment.

/kbin speaks ActivityPub but is an entirely different software stack. It has some big bugs with federation (specifically around admin actions like spam removal).

The primary instance (kbin.social) also doesn't have a very good team of mods/admins keeping up with the influx of spam.

Lemmy was about two years old when the reddit exodus happened, whereas /kbin had only been around for about a month. Its sole developer/admin is very overwhelmed just trying to keep everything running (and trying to, you know, live).

The project needs help, but I don't think Ernest has enough trustworthy people in his circle to delegate responsibilities.

Oh and the aqueducts!

The ones we're investing tons of money to replace to remove the lead?

You basically just made the case for exactly why.

Programs should be using the system resolver, not parsing that file.

The system resolver should have predictable behavior. But if other programs are doing their own DNS resolution (or otherwise predicating their functionality) based directly on the contents of resolv.conf then their behavior will not always be consistent with the system resolver (or with how the sysadmin intended things to function).

And that can break things in subtle, unpredictable ways, which is always a headache.

Thus, on some modern systems, resolv.conf simply declares the local systemd-resolved instance (i.e. 127.0.0.1) and nothing else.

A single global resolv.conf file also will not let you configure different behavior based on interface or on network namespace. Want to ensure DNS lookups for specific apps occur only through your VPN-specific DNS servers but all other apps only use the normal system resolvers (i.e. no leaking from either side of the divide)? Want to also ensure DNS lookups for those specific apps fail when the VPN is down (again, as opposed to leaking)? systemd-resolved has your back.

And before anyone asks, yes, I am aware there are other, more crude and convoluted ways to do that with e.g. iptables (just like you can use crude, inconsistent init.d spaghetti scripts to manage services). It's just one single real-world example.

A single global resolv.conf file also will not let you configure different behavior based on interface or on network namespace.

The point is to configure everything using consistent, predictable configuration files and syntax, and to ensure consistent, predictable behavior.

But if you ultimately still want resolv.conf.d back, then your distro of choice undoubtedly provides a way to do so.