It's not based on Falcon 9's engines. The propellant for this new architecture is Liquid Methane (CH4) and Liquid Oxygen. The byproducts are CO2 and H2O. The rocket can fly carbon-neutral if the CH4 is synthesized from CO2 taken from the air. Sure, there are cheaper ways to refine CH4 from natural gas, but there is a path to not use fossil fuels.
I don't see Musk hiring the TSA at his spaceports. The TSA certainly would not be in other countries. Any lines for competent screening (95% failure rate, what a joke) would be for the one and only launch that hour. Usually, delays with the TSA are due to dozens of gates all utilizing one funnel point for screening.
My 2.5 year old son actually triggered the upgrade to 11 on the family iPad, because Apple doesn't provide a way to opt out of upgrades beyond a 24 hour delay, and it popped up, right in front of the video he was watching. So please leave out this bullshit of "Apple fans wanting to test out all the shiny new features". Hell, it's sometimes easy to mistakenly tap on the intrusive dialog as an adult. It can appear while your interacting with the screen and you tap on upgrade instead.
The resolution is 2436 x 1125; which is not a 16:9 aspect ratio. Given a height of 1125, typical videos would play at 2000x1125 (or just cropped to 1920x1080). I suspect that the rounded corners and cutaway area at the top are in that remaining 436 pixel area; given the 458 DPI. So don't worry about movies being ruined. The rounded areas would't come into play.
The benefit of this 5.85" display is that the entire phone is only 5.65" in length; just 0.2" taller than the iPhone 8, and 0.6" shorter than the 8 Plus.
Not quite. You're off by two orders of magnitude.
A millisecond (ms) is 1 thousandth of a second (0.001) or 1/1,000
A microsecond (us) is 1 millionth of a second (0.000001) or 1/1,000,000
No, no, no. Unless you're suggesting that there are multiple implementations of Photon, then it's not an interface; it's a concrete implementation of Particle.
Not arguing about the C standard. But if one were to use int or long in production code at my company (rather than stdint.h types) they'd be taken out back and shiv'd in the leg; virtually speaking. We build for 5 platforms with different compilers. It's a must for portability.
So, easily debunked headlines keep the lights on, but makes everyone's blood pressure go up; which leads to needing a higher required dose of heart meds. This ultimately leads to patrons not coming back, which fails to generate ad revenue in the future.
Proper editing would make me come back more often.
I guarantee you that it's the same source code that just declares the variable as a "long" which is 4 bytes when compiled for 32-bit devices and 8 bytes when compiled for 64-bit devices. They should have used "uint64_t" which would have taken away the ambiguity and worked everywhere. It's as simple as that.
https://developer.apple.com/li...
You didn't read the parent post. Already stated that if they used stdint's uint64_t it would have been fine on all platforms. Wasn't suggesting that they should rely on Apple to save them; merely pointing out that the summary is bullshit and Apple did not cause their trouble.
There are more than 4 billion people on the planet. If everyone played just one game in that app (even just to try the app), the 31-bit value would have overflowed. So yes, I would have chosen a 64-bit number. The chess moves made, with each move time, are using substantially more space.
That would suggest that they intentionally knew that they could only support 2^31 games if trying to bit pack. They obviously used an intrinsic type of unknown size on all platforms. stdint.h and uint64_t is your friend.
Bit packing metadata into the game number is short sighted. What happens when you need to store more data per game? Steal more bits? No. Store the game state with the rest of the game data, including references to players, moves made, etc.
"Apple's decision... has caused some problems" is quite a conclusion to jump to when ignorant of the facts. If one doesn't know what they're talking about, don't make such a claim.
And to the Slashdot editors, don't even try to blame this on Apple's decision to go with 64-bit CPUs. That decision is the only reason it's NOT broken on newer devices; since the apps are compiled natively for both 32-bit and 64-bit. Otherwise ALL devices would have rolled over at 2^31.
Everyone please stop using int and long intrinsic types. uint64_t is your friend when you expect so many games. 2^31 tells me it wasn't even unsigned. How could there be a negative number of games played?
Nope. The satellites will be at an altitude of only 1,100 km; not a geostationary orbit of 35,786 km. That's only 3% latency of typical GEO satellite internet.
On top of that, the links between satellites in the mesh will run faster in the vacuum of space than through glass fiber in underwater cables.
This decision is hinging on the belief that a sequence of numbers equates to a physical key. It doesn't. If they had a better lawyer, they could argue its analog is a combination to a safe.
In regards to three-factor authentication, the courts can determine who you are (finger print, retina scan), what you have (physical key or access badge), but not what you know (combination of numbers).
Defendants in a criminal trial are not even required to take the stand for questioning.
The PCIe lanes IMHO are laid out well. There are two 40 gigabit Thunderbolt 3 (USB-C) ports on the back using 4 lanes with DisplayPort input-passthrough from any GPU. There are two gigabit Intel NICs. There is a 4 lane M.2, a 4 lane U.2, and a 4 lane PCIe slot that can all be used concurrently with 16 lanes for one GPU or 8-8 for two GPUs. One can install a 4 lane add-in card that provides another two Thunderbolt 3 ports, both with DisplayPort inputs.
So, if one wanted to, one could run a GTX 1080 with three displayports all routed through Thunderbolt 3 ports; just like a MacBook Pro, with four ports in total, with both M.2 and/or U.2 possibly in a raid.
You clearly don't understand how die stacking or package-on-package works. Single packages can have multiple NAND dies, a controller, and RAM all in one.
You must not have any children yet. Once I became a dad, I realized that my son is my time machine. I can teach him what I would have wanted to tell my younger self. He is what matters. He will live longer than me if I have anything to say about it. He will then be a dad and repeat with HIS life lessons. He is more important than me. I would give my life to save him.
Slashdot Mirror
It's not based on Falcon 9's engines. The propellant for this new architecture is Liquid Methane (CH4) and Liquid Oxygen. The byproducts are CO2 and H2O. The rocket can fly carbon-neutral if the CH4 is synthesized from CO2 taken from the air. Sure, there are cheaper ways to refine CH4 from natural gas, but there is a path to not use fossil fuels.
I don't see Musk hiring the TSA at his spaceports. The TSA certainly would not be in other countries. Any lines for competent screening (95% failure rate, what a joke) would be for the one and only launch that hour. Usually, delays with the TSA are due to dozens of gates all utilizing one funnel point for screening.
I don't see Musk hiring the TSA at his spaceports.
My 2.5 year old son actually triggered the upgrade to 11 on the family iPad, because Apple doesn't provide a way to opt out of upgrades beyond a 24 hour delay, and it popped up, right in front of the video he was watching. So please leave out this bullshit of "Apple fans wanting to test out all the shiny new features". Hell, it's sometimes easy to mistakenly tap on the intrusive dialog as an adult. It can appear while your interacting with the screen and you tap on upgrade instead.
The resolution is 2436 x 1125; which is not a 16:9 aspect ratio. Given a height of 1125, typical videos would play at 2000x1125 (or just cropped to 1920x1080). I suspect that the rounded corners and cutaway area at the top are in that remaining 436 pixel area; given the 458 DPI. So don't worry about movies being ruined. The rounded areas would't come into play. The benefit of this 5.85" display is that the entire phone is only 5.65" in length; just 0.2" taller than the iPhone 8, and 0.6" shorter than the 8 Plus.
Not quite. You're off by two orders of magnitude.
A millisecond (ms) is 1 thousandth of a second (0.001) or 1/1,000
A microsecond (us) is 1 millionth of a second (0.000001) or 1/1,000,000
No, no, no. Unless you're suggesting that there are multiple implementations of Photon, then it's not an interface; it's a concrete implementation of Particle.
Not arguing about the C standard. But if one were to use int or long in production code at my company (rather than stdint.h types) they'd be taken out back and shiv'd in the leg; virtually speaking. We build for 5 platforms with different compilers. It's a must for portability.
This is a slippery slope.
So, easily debunked headlines keep the lights on, but makes everyone's blood pressure go up; which leads to needing a higher required dose of heart meds. This ultimately leads to patrons not coming back, which fails to generate ad revenue in the future.
Proper editing would make me come back more often.
I guarantee you that it's the same source code that just declares the variable as a "long" which is 4 bytes when compiled for 32-bit devices and 8 bytes when compiled for 64-bit devices. They should have used "uint64_t" which would have taken away the ambiguity and worked everywhere. It's as simple as that.
https://developer.apple.com/li...
You didn't read the parent post. Already stated that if they used stdint's uint64_t it would have been fine on all platforms. Wasn't suggesting that they should rely on Apple to save them; merely pointing out that the summary is bullshit and Apple did not cause their trouble.
There are more than 4 billion people on the planet. If everyone played just one game in that app (even just to try the app), the 31-bit value would have overflowed. So yes, I would have chosen a 64-bit number. The chess moves made, with each move time, are using substantially more space.
That would suggest that they intentionally knew that they could only support 2^31 games if trying to bit pack. They obviously used an intrinsic type of unknown size on all platforms. stdint.h and uint64_t is your friend.
Bit packing metadata into the game number is short sighted. What happens when you need to store more data per game? Steal more bits? No. Store the game state with the rest of the game data, including references to players, moves made, etc.
"Apple's decision ... has caused some problems" is quite a conclusion to jump to when ignorant of the facts. If one doesn't know what they're talking about, don't make such a claim.
And to the Slashdot editors, don't even try to blame this on Apple's decision to go with 64-bit CPUs. That decision is the only reason it's NOT broken on newer devices; since the apps are compiled natively for both 32-bit and 64-bit. Otherwise ALL devices would have rolled over at 2^31.
Everyone please stop using int and long intrinsic types. uint64_t is your friend when you expect so many games. 2^31 tells me it wasn't even unsigned. How could there be a negative number of games played?
Vandenberg AFB is federal land, so wouldn't that mean the origin is out of jurisdiction as well?
And a lot of latency.
Nope. The satellites will be at an altitude of only 1,100 km; not a geostationary orbit of 35,786 km. That's only 3% latency of typical GEO satellite internet.
On top of that, the links between satellites in the mesh will run faster in the vacuum of space than through glass fiber in underwater cables.
I completely agree.
This decision is hinging on the belief that a sequence of numbers equates to a physical key. It doesn't. If they had a better lawyer, they could argue its analog is a combination to a safe.
In regards to three-factor authentication, the courts can determine who you are (finger print, retina scan), what you have (physical key or access badge), but not what you know (combination of numbers).
Defendants in a criminal trial are not even required to take the stand for questioning.
Was the defendant Mirandized as in, "You have the right to remain silent"? One cannot be compelled to speak.
M.2 is a form factor. M.2 SSDs can run either the AHCI or NVMe protocol over 4 PCIe lanes.
M.2 is a better option BECAUSE it supports NVMe.
Preface: I'm not a shill, just excited for this product. I'm seriously considering this board for a Hackintosh.
I give to you, the Gigabyte GA-Z170X-Designare
The PCIe lanes IMHO are laid out well. There are two 40 gigabit Thunderbolt 3 (USB-C) ports on the back using 4 lanes with DisplayPort input-passthrough from any GPU. There are two gigabit Intel NICs. There is a 4 lane M.2, a 4 lane U.2, and a 4 lane PCIe slot that can all be used concurrently with 16 lanes for one GPU or 8-8 for two GPUs. One can install a 4 lane add-in card that provides another two Thunderbolt 3 ports, both with DisplayPort inputs.
So, if one wanted to, one could run a GTX 1080 with three displayports all routed through Thunderbolt 3 ports; just like a MacBook Pro, with four ports in total, with both M.2 and/or U.2 possibly in a raid.
You clearly don't understand how die stacking or package-on-package works. Single packages can have multiple NAND dies, a controller, and RAM all in one.
You must not have any children yet. Once I became a dad, I realized that my son is my time machine. I can teach him what I would have wanted to tell my younger self. He is what matters. He will live longer than me if I have anything to say about it. He will then be a dad and repeat with HIS life lessons. He is more important than me. I would give my life to save him.
I stopped reading after "Facebook spacecraft". The humor needs to come before the ignorance.