Yeah, though it looks like the cyan (which would be ~500nm) is actually false color UV image, judging by the same color scale as this https://www.nasa.gov/image-detail/5-3-2024_sdo_x1pt6_flare_131/
Yeah, though it looks like the cyan (which would be ~500nm) is actually false color UV image, judging by the same color scale as this https://www.nasa.gov/image-detail/5-3-2024_sdo_x1pt6_flare_131/
Some numbers are missing…[due to] out of memory error.
The S7+ seems to have 6 or 8GB RAM, but the iPhone 7 only has 2, yet it seems the iPhone ran the test and the S7+ didn’t. I wonder if the iOS implementation is that much better, or Android isn’t set up with any swap, or…?
I know the “attack helicopter” bit is a transphobic trope, but given how hard those fans are probably working, I think this computer might actually identify as one.
(If this comment is offensive I can remove it/mod can obviously remove it — not trying to be a dick!)
Human gestation is 10 months
“Full term” pregnancy is ~40w from last menstrual period, or ~38w from conception. There are ~4.345 weeks/month, putting full term at ~8.75 to ~9.2 months. Note the 9.2 months includes ~2 weeks before fertilization.
(Not sure if I’m being whooshed or not…)
People praise the female reproductive system as miraculous because it can make a baby in only 9 months. Like that’s neat and all, but my reproductive system can make a baby in approximately 13 seconds, so I don’t see what all the fuss is about.
Yep, you’re right — I was just responding to parent’s comment about fiber being best because nothing is faster than light :)
That’s…not really a cogent argument.
Satellites connect to ground using radio/microwave (or even laser), all of which are electromagnetic radiation and travel at the speed of light (in vacuum).
Light in a fiber travels much more slowly than in vacuum — light in fiber travels at around 67% the speed of light in vacuum (depends on the fiber). In contrast, signals through cat7 twisted pair (Ethernet) can be north of 75%, and coaxial cable can be north of 80% (even higher for air dielectric). Note that these are all carrying electromagnetic waves, they’re just a) not in free space and b) generally not optical frequency, so we don’t call them light, but they are still governed by the same equations and limitations.
If you want to get signals from point A to point B fastest (lowest latency), you don’t use fiber, you probably use microwaves: https://arstechnica.com/information-technology/2016/11/private-microwave-networks-financial-hft/
Finally, the reason fiber is so good is complicated, but has to do with the fact that “physics bandwidth” tends to care about fractional bandwidth (“delta frequency divided by frequency”), whereas “information bandwidth” cares about absolute bandwidth (“delta frequency”), all else being equal (looking at you, SNR). Fiber uses optical frequencies, which can be hundreds of THz — so a tiny fractional bandwidth is a huge absolute bandwidth.
80% of the USA lives within urban areas (source). Urban “fiberization” is absolutely within reach.
Agree that running fiber out to very remote areas is tricky, but even then it’s probably not prohibitive for all but the most remote locations.
So the irony is
I see what you did there…
Left pedal looks more like a dead pedal to me.
And as others have said, change in direction is still acceleration. That’s part of Newton’s (apocryphal?) apple story — he witnessed an apple falling, and wondered why the moon doesn’t also fall. His amazing insight is that it does fall (accelerate), it’s just that it falls in such a way that it orbits, rather than hits, the Earth (for timescales relevant to a human).
I think you mean more scrupulous, not less.
I hope I’m wrong! I’d definitely consider buying some — hopefully you can report back with results. If they’re slower than advertised but have the actual capacity that’d still be awesome!
This looks like it might be it:
The drive doesn’t provide 4TB of storage either, considering the single NAND chip. That means if you were to attempt to write that much data to the SSD, at some point it would either fail or start overwriting existing data.
I’d say it gets a little different with command line utilities — maybe “utility” is the appropriate term here, but I’d call something like grep
a program, not an application (again — “utility” also works).
To be sure, grep
is extremely powerful, but its scope is limited.
Others mentioned virtualization — I have had issues with COW filesystems (btrfs), as COW does not always play nicely with VM drives (extreme fragmentation and very poor performance).
from stdlib.h import cout
Wait this looks wrong, shit…
Anything can use it, but I think by convention it’s used for http on a non-privileged port.
Maybe there’s some interplay between amd64 and x64 architectures.
AMD64 and x64 are the same thing. Do you mean AMD64 and x86? There is definitely interplay there, as AMD64 implements the x86-32 instruction set.
It is “backwards” from some other commands — usually you run copy/rsync/link from source to destination, but with tar the destination (tarball) is specified before the source (directory/files).
That, and the flags not needing dashes always just throws me for a loop.
And the icing on the cake is that I don’t use tar for tarring that often, so I lose all muscle memory (untaring a tgz or tar.bz2 is frequent enough that I can usually get that right at least…).
But they’re only equal in the Turing complete sense, which (iirc) says nothing about performance or timing.