In case anyone is looking for alternatives, there's a well-maintained fork of neofetch called hyfetch. There's also a neofetch clone written in C called fastfetch.
Using shift for erase isn't a great choice. In many terminals, holding shift prevents mouse input from going to the running program, and instead allows you to use the terminal's text selection functionality.
The problem is that the Sun is significantly brighter now than it used to be back then, so the amount of heating from the same amount of methane/co2 is proportionally more now too
Since the Sun settled onto the Main Sequence after its formation, it has gradually brightened. It is now 30% brighter than it was then.
The brightening is caused by accumulation of helium ash in the Sun's core. This causes the core's equilibrium state to be denser and hotter, with more energy being produced.
In another billion years or so, this will drive the Earth into a runaway greenhouse effect. The oceans will evaporate and the hydrogen will be lost to space. Not long after, the Earth will be a dead planet devoid of any life, even microorganisms. You sometimes see statements about how when the Sun expands into a red giant it will destroy life on Earth, but the Earth will have long been lifeless by that time.
In case others were curious about the term Helium ash:
Ash is the name given to the energetic alpha-particles or helium nuclei produced by fusion reactions in a deuterium-tritium plasma, even though helium bears no physical resemblance to ash from a fire.
It should be noted that deuterium-tritium fusion is not what is happening in the Sun. The primary reaction chain involves proton-proton fusion, which yields deuterium. The deuterium immediately (within seconds) reacts with another proton to make helium-3. Helium-3 eventually fuses with another He-3 to make He-4 and two protons. There are some side chains, but the ultimate overall reaction is four protons + 2 electrons --> 4He + 2 neutrinos.
The way I read it, it isn't a co2 greenhouse, in fact the death stroke is the increased co2 absorption at those temperatures due to weathering of rock. Driving co2 below what plants can survive. Building a parasol at l1 that can be modulated to vary what is passed and what is harvested will be necessary at some point. It could get a couple extra billion years potentially.
Anyone else question why astronomers are so sure about things that happened 5+ billion years ago ? I guess otherwise there’d be a probably or a maybe in every sentence ? But then how do you tell when they really are sure ?
There is always an implied "as far as we know". But astronomy has a couple reasons to be fairly certain about many things. We can see a lot of stars, and because light takes time to travel the further away they are the older the state we are observing. We only see each star as it is right now, but from looking at a lot of them you get a good idea of how they can develop. Like how you can get a good idea of how humans age by just looking at a lot of people of different ages; you don't need to follow each of them for 90 years. The other advantage is that most of it is well understood physics that can be reasoned about and simulated. And then we can compare those simulations to what we are observing across the universe to see if our simulations make sense.
Science is forming a testable hypothesis and then testing it. So you hypothesize "as stars accumulate fusion products their cores get heavier and the rate of fusion increases, making them brighter" and test this both with modeling and looking if this matches the stars we can see. How is that now science?
They build a model of the universe's laws, as simple as they can get it while matching the evidence. They then look at other evidence they hadn't looked at before. It turns out, that quite simple models can predict a lot of different phenomena, which makes us reasonably confident in our assumptions that (1) the universe is governed by simple, fundamental laws; and (2) those laws are similar to our model.
If we make the assumption that our model applies everywhere and at every time (colloquially, that the laws of physics don't change), we can ask our models what happened in the past. Under our assumption, that's probably quite close to what actually happened. This assumption is called the "principle of induction", the "uniformitarian principle", the "cosmological principle", the "Copernican principle", and many other things besides.
The models are so good that when solar neutrinos were not as predicted, it turned out to be because of new physics (neutrino oscillation) not flaws in the solar model.
Sunspot cycles are sometimes mentioned as a possible factor in climate change, especially by those skeptical of human generated causes. The downvoters might have mistaken the comment as being related to this instead of being a different solar variable.
There's nothing that forces a Wayland compositor to be written in C. I've seen ones written in C++, Zig, and Rust, but you could really use any language as long as you can still call the appropriate system/kernel APIs
Nothing preventing you from writing a X11 server in something else either (and people have done so!). But fact is, most wayland compositors right now are either pure C or C++ (and I think the rest uses at least wlroots?).
Many X11 window managers are written in non-c languages too and I don't think I am too far off the mark when I say that a decent fraction of wayland compositors would just be external window managers if there existed a standardized interface for window managers when they were written (I think some compositors have an interface for external window managers now, but is there a standard interface by now?).
The question here isn't about damage but about what mechanisms in the "pain pathway" are responsible for OP's specific experience of this pain. One day he has sudden, debilitating pain - in both wrists - in the absence of a traumatic event. He's conspicuously omitted any kind of medical diagnosis, and the whole thing is part of an existential crisis on the tail end of an insane, psychologically unsustainable workload. Not a typical presentation of RSI, that's for sure.
