It was more the math itself and the simulations and that kind of thing that I was looking for, but I probably could've made that more clear, sorry. I appreciate your answer though, the exact vastness wasn't something that dawned on me outside of basic planetary science taught in school.

I don't know how to give best answer of if that's even a power that I have on my post but this is definitely it so far, thank you! This is exactly the type of comprehensive breakdown that I was looking for.

this is the only correct response

hyperventilating makes you blow off too much carbon dioxide. breathing into a bag forces you to rebreathe that CO2, which keeps the balance of CO2 in your blood closer to normal. too little CO2 in your blood makes your blood too alkaline, which is not good for all the chemical reactions happening in your body.

the purpose isnt to make you breathe slower, it’s preventing respiratory alkalosis

[removed]

OP's question also brings to mind the story of the Curiosity Opportunity rover on mars.

It's original tenure was only supposed to be a 90 day mission on the surface, but through a combination of good construction and non-catastrophic conditions, it instead served for 14 years. It didn't stop until a harsh dust storm knocked out its ability to recharge.

Similarly, something like the Voyager is a combination of "let's get it as far as we can" and "let's see how far it will go". With enough computation and simulation, a path can be plotted out of our star system so that it doesn't hit Pluto and crash. However the farther it goes, the more Chaotic Entropy comes into play. We can project paths of celestial bodies, but longer predictions bring on more deviations until it stops being viable.

Once Voyager cleared the system, it was reasonable to say "alright, we've set it up as best we can, let's see where it goes" and keep collecting data as long as it transmits

As well as all the fancy math the book smart people do, space is vast and empty. Like REALLY vast and empty. Unconceivably vast and empty. Now I know your picturing in your head something vast and empty, but its nowhere near the level that space is. You can fit every planet in our solar system, equator to equator, between Earth and the Moon, and that's not even a drop in the bucket compared to the space of...well...space

Just a warning that all the clinical evidence provided in that review was done by (or funded by) companies using their own products. It's a major issue in a lot of dermatological research as noted by this article from Harvard (https://www.hsph.harvard.edu/nutritionsource/collagen/).

It's worth noting that the American Academy of Dermatology has no recommendations regarding dietary collagen but does have evidenced backed advice for those looking to maintain healthy skin:

https://www.aad.org/public/cosmetic/younger-looking/firm-sagging-skin

https://www.aad.org/public/everyday-care/skin-care-secrets/anti-aging/reduce-premature-aging-skin

Short Answer: There is an index.

Long Answer: The index is in a fixed location on the disk so the drive knows where to look for it every time. Then for variable width files (images, video, music, text docs) the index gives starting/stopping locations around the disk as files are rarely contiguous these days, especially since SSDs came out. The disk then knows how to translate the start/stops/inbetweens to exact (positions on platters, locations on chip) where the 0/1's are stored to then stream the file as requested.

Sure but just because it's unlikely for a commet or asteroid to hit them or something doesn't mean that it's impossible, did they do anything with the orbital paths of the planets around the sun to know that when they launched it it wasn't going to be swept into the orbit of another planet? If so, what did they do?

And thank you I didn't know that about Voyager I!

We do not know that, just that it will ake a very long time before it could because of the enormous distances.

Voyager, I do orbit something, the core of the galaxy just like the solar system. It is the combined effect of all matter in the solar syst.

There is an extraordinary amount of math involved. They plan out the exact path of the vessel, as well as the paths of all planets involved.

The approximate path of the vessel is calculated with conic sections (ellipses and hyperbolas) around a planet or star.

The best way to predict a path, albeit with an extraordinary amount of math, is actually very simple. We use the conic sections to predict planets' orbits, since they don't tend to change much, and then we do a very simple calculation to see how much they each tug on the vessel. We then add all of these tugs together and see what direction it is pulled overall. We move it a tiny forward, and repeat the calculation again. Move it again. Calculate, move, calculate. Over and over ten billion times to get a good prediction of the path the vessel will follow. Computers are great for that.

The resistance to exhaling and inhaling adds more rhythm to your breathing. Hyperventilation is you breathing in and out too fast, leading to bad gas exchange. The bag forces you to breathe slower. The bag doesn't actually do anything more, than someone looking in to your eyes, and commanding you to "inhale... exhale.... inhale... exhale..."

This is why people with panic disorders (like me), are taught some breathing rhythm thing we can exercise. I myself use "breathe only through the nose and fully exhale and inhale" (Harder than you think, and I played the french horn and tuba for +10 years - I got good capacity). Full inahle and exhale also activates you parasymphatic nervous system and calms you down.

It is just about the feeling of gaining control, giving you something to focus on that keeps you present.

The bag tricks isn't even recommended anymore, since people forgot that they'd actually also need to breathe oxygen in. Leading them to be more likely to pass out from lack of oxygen. Also doesn't actually teach you methods. of controlling your emotions, but instead forcing you to rely to a tool. And if you don't have that tool to get comfort and control from, it makes things worse.

[removed]

[removed]

Your submission has been removed for the following reason(s):

ELI5 is not for straightforward answers or facts - ELI5 is for requesting an explanation of a concept, not a simple straightforward answer. This includes topics of a narrow nature that don’t qualify as being sufficiently complex per rule 2.

If you would like this removal reviewed, please read the detailed rules first. If you believe this {kind} was removed erroneously, please use this form and we will review your submission.

Not dumb, a great question.

On the microprocessor level the hardware is designed to always read a certain number of digits, called "bits" in this case, and 4 bits become a "nibble", 8 bits are a "byte".

So a 16 bit microprocessor would read the value "one" as

0000 0000 0000 0001

and read "ten" as

0000 0000 0000 1010

So in older days, the processor size was a big deal, I played a lot of video games so I remember that the Nintendo was 8-bit, we then 16-bit systems (Sega and Super Nintendo). and then 32/64 bit processors with Nintendo 64, etc.

For the most part we've stuck at 64 bit for our processors for many reasons.

[deleted]

This is not at all how bingo works.

It's divided up, and any remaining space is filled with zeroes.

You may have heard the terms "bit," "byte," "megabyte," etc. A bit is one digit; a byte is 8 digits, and multiples of that are named with their SI prefixes ("kilobyte", "gigabyte", etc).

So when the computer reads, it's reading in multiples of 8 digits. In your case, the computer might read one byte that has the binary data "1001" stored in it. To the computer, this would show up as "00001001", but 2 would just be "00000010" and 1 would be "00000001."

Note that I'm talking about bytes for simplicity, but computers generally run off a "word" size (which is itself some multiple of 8 bits), and sometimes the first digit is flipped to 1 even if the data doesn't fill the whole space. You can ignore that for now, that's not important for this answer. Specifics aside, the point is that the computer is reading specific numbers of digits at a time and the data is padded with 0s if it doesn't fill all of the digits the computer's reading.

Me too. Boom needs to keep us posted on his Health Journey.

Or else I will have a Sad.

At the absolute lowest level, it's built into the architecture of the system - when we say a "32-bit" or "64-bit" processor or architecture, what we are saying is that the native instruction set is encoded in that number of bits, with a bit being a discrete 1 or 0 - in other data sets that don't need that much, we will have code that defines the length of a piece of data.

Best thing you can do for your skin is use sunblock and exfoliate. I wish I knew that when I was younger

You’re completely correct that it could either be 9 or a 2 then a 1. The issue is that you’re assuming that the is no context.

In storage, there are conventions (e.g. ASCII) that say that basic text is 8 bits per letter. Similarly, other data is stored in fixed-length intervals.
In RAM, whoever is writing to it determines how it is used. It could be any length. The program (and programmer) using it needs to make sure they’re using it correctly.

There are also ways to compress things like text, where bit length is dynamic. But that’s a bit complex, so let me know if you want that explanation as well.

Radiant!

Depends on what it's reading. If it knows in advance to expect ASCII text, then it will count out 8 bits to each letter.

The simplest ruleset which doesn't limit you at all would be that, after ten letters, there is a single bit which says whether or not the message continues. This ruleset is inefficient as hell but shows a simple solution.