Information cannot move through any point in space faster than c. That simple. If you want to go faster than c, then you need to move the points instead of moving through them.
One of the first things told during freshmen inauguration was plagiarism almost always resulted in academic probation for 1-2 semesters depending on the severity, and cheating got you banned for life from all state Universities, and any degrees you may have gotten from them will be revoked.
The order of events do not always agree for all frames, but I assume that they'd have to agree for the ordering of certain related events for causality to work, but that may not be true either.
An example is assume there is a train, a tunnel, and another observer. Assume the train is longer than the tunnel. Now assume the other observer is watching the tunnel from a perpendicular view.
If the train is moving very fast, it will contract in the direction of its movement. From the perspective of the other observer, the train is shorter than the tunnel, but from the perspective of the train, the tunnel is shorter than the train. Now if this tunnel has the ability to close its entry and exist. from the other observer, both the entry and exit can close at the same time and the entire train fits within the tunnel, then the exit and re-open and allow the train to exit the tunnel.
From the perspective of the train, the exit closes first, then right before the train reaches the exit, the exit door opens, then the entry closes.
The events have a different ordering, they have to, because they cannot agree on the lengths.
Lorentz contraction and relativity only applies to objects moving through space. These distant objects are not moving through space. "extra redshift because of time dilation due to its speed" WTF does that even mean? When light gets emitted by an electron, it is the exact same, you know, quantum. The frequency of light is not affect by time dilation at all, it is only affected by red shifting.
Your link says " then find that the rest of the universe is moving away at very high speeds, approaching (but not exceeding) the speed of light", but we already see galaxies moving away over 2x the speed of light. Since these galaxies are technically not moving through space quickly, they experience little time dilation.
Newer hardware supports millions to tens of millions of times per seconds. My home firewall is kept withing 0.1ms of a remote NTP server that's about 2000 miles away round trip. It's a hardware tick that is programmable and can schedule interrupts. The OS can check the current counter to see how much time has elapsed since the last check, and NTP clients can adjust the frequency to adjust for skew.
One way to "fix" that issue is to not have time go backwards, but make time tick more slowly until real time catches up. Servers should be closer to seconds out of sync. Several of my home systems are less than 1ms out of sync with remote servers 80+ ms away from me.
Deduplication is at the block level. You would need to have all of your code segments block aligned, which could be an issue since block sizes vary from 512bytes to over 1MB depending on your FS and how you formatted it.
15min is horrible, many protocols become insecure after a short while. Replay attacks! Time being out of sync is a huge security issue. Nearly every security protocol needs to know what time it is. The more accurate your time, the more secure you can make it by reducing the attack window.
OpenNTPD added a feature that allows it to query a pool of configurable HTTPS servers, finds a median reported current time(HTTPS reports time as part of the protocol), then attempt to use NTP and requires that the answer from NTP is within a small distance of the HTTPS pool. This way another server can't fake time too far out.
In the past year, OpenNTPD has added some features and can now regularly maintain time within 5ms with a modern system. OpenNTPD does rely on well implemented hardware a bit more and doesn't try to do fancy adjustments for poorly implemented hardware clocks or older hardware, but it does a decent job clock steering with newer hardware.
From what little I've read, getting time right is incredibly hard, and this guy has a huge bank of knowledge and practice in his head. Anyone who thinks they can take on what he does probably doesn't understand the issues at hand. He's one of those rare 0.01% of programmers who actually know WTF he's doing.
Average and even median pay can be deceptive. Without knowing where those people live or what kind of working environments they have to put up with, it's hard to gauge the value of that $200k.
They do from time to time use the term "remap", but in a way that indicates the block was removed from the pool. It's probably not a correct term, but it's one that most people would understand.
You can never fully disable the Windows swap, it is hard coded into the kernel that is must exist or the kernel will not work. Even if it claims to be disabled, it still creates a 32MB page file on the boot drive, and can thrash the heck out of it. Win8.1 won't even let me reduce the page file below 800MB. I tried disabling it and it said it'll still create an 800MB page file.
You also have issues with memory fragmentation. If there is not a large enough contiguous free memory address, the OS can page out and do some minor defragging. It is relatively simple to contrive a situation where 50% of your memory is in use, but you'll get an out of memory error trying to allocate a page larger than 4KB. In the real world, the 80/20 rule is at play. Once you get past 80% usage, you could start running into memory issues with out a swap scratch pad.
Slashdot Mirror
Modern digital dental x-rays have 80%-90% reduction in total radiation over the prior generation.
Information cannot move through any point in space faster than c. That simple. If you want to go faster than c, then you need to move the points instead of moving through them.
One of the first things told during freshmen inauguration was plagiarism almost always resulted in academic probation for 1-2 semesters depending on the severity, and cheating got you banned for life from all state Universities, and any degrees you may have gotten from them will be revoked.
Relative to our frame of reference, there are objects moving away form us faster than 2c.
The order of events do not always agree for all frames, but I assume that they'd have to agree for the ordering of certain related events for causality to work, but that may not be true either.
An example is assume there is a train, a tunnel, and another observer. Assume the train is longer than the tunnel. Now assume the other observer is watching the tunnel from a perpendicular view.
If the train is moving very fast, it will contract in the direction of its movement. From the perspective of the other observer, the train is shorter than the tunnel, but from the perspective of the train, the tunnel is shorter than the train. Now if this tunnel has the ability to close its entry and exist. from the other observer, both the entry and exit can close at the same time and the entire train fits within the tunnel, then the exit and re-open and allow the train to exit the tunnel.
From the perspective of the train, the exit closes first, then right before the train reaches the exit, the exit door opens, then the entry closes.
The events have a different ordering, they have to, because they cannot agree on the lengths.
Lorentz contraction and relativity only applies to objects moving through space. These distant objects are not moving through space. "extra redshift because of time dilation due to its speed" WTF does that even mean? When light gets emitted by an electron, it is the exact same, you know, quantum. The frequency of light is not affect by time dilation at all, it is only affected by red shifting.
CDMA is superior to GSM is nearly every way except cost.
Your link says " then find that the rest of the universe is moving away at very high speeds, approaching (but not exceeding) the speed of light", but we already see galaxies moving away over 2x the speed of light. Since these galaxies are technically not moving through space quickly, they experience little time dilation.
1000 NTP clients would average about 1Kbits/s total. You're going to need a whole lot of "internet of things" before bandwidth becomes an issue.
Newer hardware supports millions to tens of millions of times per seconds. My home firewall is kept withing 0.1ms of a remote NTP server that's about 2000 miles away round trip. It's a hardware tick that is programmable and can schedule interrupts. The OS can check the current counter to see how much time has elapsed since the last check, and NTP clients can adjust the frequency to adjust for skew.
One way to "fix" that issue is to not have time go backwards, but make time tick more slowly until real time catches up. Servers should be closer to seconds out of sync. Several of my home systems are less than 1ms out of sync with remote servers 80+ ms away from me.
We want interactive content that can do perceptibly real-time processing. Static content is for books.
SystemTime = CurrentDataBaseTime
Delay = LocalTime - SystemTime - TimeDifference
TimeDifference = LocalTime - SystemTime - Delay
Now = LocalTime - TimeDifference
There, corrected it for you. Now you try to figure this problem out.
I thought an "affect" creates a specific "effect". I like pixels shaders that affect the graphics by creating a shiny graphical effect.
How do you maintain relational constraints? I love constraints of all kinds, saves me a lot of time from bugs messing up data.
Deduplication is at the block level. You would need to have all of your code segments block aligned, which could be an issue since block sizes vary from 512bytes to over 1MB depending on your FS and how you formatted it.
When most Americans talk, they sound unintelligent. Is that the same thing?
15min is horrible, many protocols become insecure after a short while. Replay attacks! Time being out of sync is a huge security issue. Nearly every security protocol needs to know what time it is. The more accurate your time, the more secure you can make it by reducing the attack window.
OpenNTPD added a feature that allows it to query a pool of configurable HTTPS servers, finds a median reported current time(HTTPS reports time as part of the protocol), then attempt to use NTP and requires that the answer from NTP is within a small distance of the HTTPS pool. This way another server can't fake time too far out.
In the past year, OpenNTPD has added some features and can now regularly maintain time within 5ms with a modern system. OpenNTPD does rely on well implemented hardware a bit more and doesn't try to do fancy adjustments for poorly implemented hardware clocks or older hardware, but it does a decent job clock steering with newer hardware.
From what little I've read, getting time right is incredibly hard, and this guy has a huge bank of knowledge and practice in his head. Anyone who thinks they can take on what he does probably doesn't understand the issues at hand. He's one of those rare 0.01% of programmers who actually know WTF he's doing.
OpenNTPD is SNTP only, but also adjusts for clock drift. Actually, OpenNTPD adjusts the clock's tick rate instead of only adjusting the time.
Average and even median pay can be deceptive. Without knowing where those people live or what kind of working environments they have to put up with, it's hard to gauge the value of that $200k.
They do from time to time use the term "remap", but in a way that indicates the block was removed from the pool. It's probably not a correct term, but it's one that most people would understand.
You can never fully disable the Windows swap, it is hard coded into the kernel that is must exist or the kernel will not work. Even if it claims to be disabled, it still creates a 32MB page file on the boot drive, and can thrash the heck out of it. Win8.1 won't even let me reduce the page file below 800MB. I tried disabling it and it said it'll still create an 800MB page file.
You also have issues with memory fragmentation. If there is not a large enough contiguous free memory address, the OS can page out and do some minor defragging. It is relatively simple to contrive a situation where 50% of your memory is in use, but you'll get an out of memory error trying to allocate a page larger than 4KB. In the real world, the 80/20 rule is at play. Once you get past 80% usage, you could start running into memory issues with out a swap scratch pad.