This is the moment where Margaret Brennan asks the question. https://youtu.be/IvSZTiAZ3NY?t...

Hollow core fiber

Why do you assume that the hardware running the simulation has problems with keeping the state of every particle in the universe?

Not even GNU C, the kernel is written in kernel C and C compilers have to be adapted to be able to compile it correctly.

GCC and Clang are the only compilers that work. There used to be support for icc as well, but compiler-specific tweaks are required for every compiler, and it was not worth the effort.

Norway is almost 100% hydro. They don't need nuclear, they just need to stop selling oil to everyone else.

We aren't leading when we are emitting 10 times (or more) per capita than the typical underdeveloped country.

Your comments refer to my original statement:

"There are a bunch of ways to get IPv6 transported in an IPv4-only network, but getting IPv4 transported in an IPv6-only network is not nearly as well supported. IPv6 will always be an afterthought if you have to implement a full IPv4 backbone anyway, before you can start doing IPv6."

Your statements about IPv4 and IPv6 being completely separate are either simply wrong or irrelevant, depending on how they are interpreted. Right now, with most equipment, a full-service ISP who wants to deliver pure IPv6 services has to start by building an IPv4 network.

Several governments have required IPv6 for years. However, almost many vendors see it as a tickbox item which will not be used much in practice. They implement precisely enough to get past the requirements, but many quality of implementation features are missing.

Mobile networks are the exception; they expect IPv6 to actually work and get used.

This is so not true. Lots of ISPs run IPv6 on top of IPv4+MPLS. You hardly have to touch your backbone at all to get that working; it has been supported for a decade on almost all relevant equipment.

The modern solution is to ditch MPLS and do IPv4 as an overlay on IPv6 with segment routing. That way you only have to worry about one protocol (IPv6) in the backbone. However, vendor support for that is very much lacking.

The crackle and the faint background noise of a vinyl record is comforting and nostalgic, and therefore better. Also, the act of physically taking a recording out of its sleeve and putting in on the player prepares the mood for listening.

Luckily crackle, noise, and physicality are features that come with even the cheapest of record players. If anything, you get less with the really expensive systems.

Many core routers still do not have full feature parity between IPv4 and IPv6, on the latest software release. Even new models.

There are a bunch of ways to get IPv6 transported in an IPv4-only network, but getting IPv4 transported in an IPv6-only network is not nearly as well supported. IPv6 will always be an afterthought if you have to implement a full IPv4 backbone anyway, before you can start doing IPv6.

Exactly! The people writing the article and most people commenting are the insane ones. We don't need to stop improving lives for everyone, we just need to stop fucking up. Human development requires energy. Once we have that energy, almost anything is possible, including keeping the Earth healthy.

Accessibility in Linux is very far behind Windows. There is work being done, particularly by Red Hat, but for almost everyone else it is low priority and therefore doesn't happen. Installers are particularly low priority for accessibility.

If you really want to use Linux, you will likely need someone with good eyesight to do the installation and the basic accessibility configuration. I tried the built-in screen reader in Gnome, and it was unfortunately not very good.

Did they? Where can I get third party clients for WhatsApp, Facebook Messenger or Teams?

The only thing systemd-resolved has to do with an init system is the strange name. Naming is one of the things that bothers me about systemd...

Uninstall systemd-resolved if you don't like it, but it is actually a really good resolver.