Comment Re:Test run (Score 3, Funny) 52
Haha, no. Humans' collars are already here, we just keep them in our pockets and pay for them ourselves.
Haha, no. Humans' collars are already here, we just keep them in our pockets and pay for them ourselves.
I think you'd be hard-pressed to find a company that doesn't hide things. The difference between Anthropic and (insert company here) is only that Anthropic leaked their source code, so now we can see what they kept hidden.
Psycho-active pharmacological effects come from dozens of substances working together in the source of each drug. To pull just one gene from 5 difference drug sources seems like a "can this be done?" experiment, not a procedure aimed at producing a desired product.
The thing with most countries that aren't america is you cant just unilaterally change a contract even with "30 days notice", you need to get the customer to actively consent, click a button that says "I acknowledge this nonsense" or whatever. Netflix was fined for breaking Italian law, in Italy.
Netflix are absolutely NOT in the right, and that should not be controversial to anyone
If you can't figure out for yourself what's wrong with ordering large numbers of men to their deaths, then I won't be able to explain it to you.
Yes there is, it's hardware and driver version dependent. It's far more efficient to just do the compilation in the background than to keep a precompiled version for each game for each combination of hardware and driver, x2 once for Vulkan and once for DirectX for games which support both.
They could take that one step further: once your computer has compiled the appropriate shader for its particular combination of hardware/driver/etc, the game could upload that particular shader to a repository, so that the next install with the exact same combination of conditions could just download it instead of having to duplicate the work. I imagine there are a lot of people out there running functionally identical systems that would benefit.
I suppose they don't do that because they don't trust people not to repurpose the mechanism as a malware vector, or something.
U scared bro?
He's probably not scared enough. Anyone old enough to remember Vietnam knows how the song goes from here. "We must throw another batch of American men into the meat grinder, otherwise the lives of the previous batch will have been sacrificed in vain", and repeat ad infinitum.
Turning to AIs for a ruling on who is human and who is not is an interesting inversion of the Turing test.
You're confusing the importance of avoiding Kessler syndrome in LEO with the difficulty of causing Kessler syndrome. GEO debris can potentially remain there for millions of years before interactions between the gravitational pull of the Sun, Earth, and Moon sufficiently perturb it. LEO debris remains for weeks to months. You have to have many orders of magnitude more debris in LEO to trigger Kessler Syndrome, where the rate of collisions exceeds the rate of debris loss.
The fact that a LEO Kessler Syndrome would also be short is something that exists on top of that.
It's also worth nothing that not only are modern satellites not only vastly better at properly disposing of themselves than they were in the 1970s when Kessler Syndrome was proposed, but they're also vastly better at avoiding debris strikes. All of these factors are multiplicative together.
Lol, I was thinking of this instead
People forget that the primary concerns about Kessler Syndrome were about geosynchronous orbit, which used to be where all the most important satellites went (many of course still go there, but not the megaconstellations). It takes a long, long time for debris to leave GEO. But LEO is a very different beast.
They said it's internal rather than a collision, so probably a failed COPV would be my guess.
Yeah. In particular:
with fragments likely to fall to Earth over the next few weeks
LEO FTW. Kessler Syndrome is primarily a risk if you put too much stuff with too poor of an end-of-life disposal rate in GEO. End-of-life without proper disposal rates have declined exponentially since Kessler Syndrome was first proposed (manufacturers both understand the importance more, and do a better job, of decreasing the rate of failures before deorbit - in the past, sometimes there wasn't even attempts to dispose of a craft at end-of-life). And now we're increasingly putting stuff in LEO, where debris falls out of orbit relatively quickly. It's not impossible in LEO, esp. with higher LEO orbits - but it's much more difficult.
Or to put it another way: fragments can't build up to hit other things if they're gone after just a couple weeks.
And this trend is likely to continue - a lower percentage of premature failures, and decreasing altitudes / reentry times. Concerning ever-decreasing altitudes, we've already been doing this via use of ion engines to provide more reboost (with mission lifespans designed for only several years before running out of propellant, instead of decades like the giant GEO ones), but there's an increasing interest in "sky skimming" satellites that function in a way somewhat reminiscent of a ramjet - instead of krypton or xenon as the propellant for an ion engine, the sparse atmospheric air itself is the propellant, so the craft can in effect fly indefinitely until it fails, wherein it quite rapidly enters the denser atmosphere and burns up.
Some researchers do think we are actually pretty close to a kessler event from musks increasingly rampant space polution.
With that said, if it happens, it wont be long term. The LEO orbit they take means the sky will mostly clear up in well under a decade with most of the debris having deorbited in around 5 years.
I wont even speculate on the sort of havok Elon musks fantastical and unlikely space datacenters would create.
Next up : Who needs Oracle if you can have PostgreSQL
Fixed that for you
Your good nature will bring you unbounded happiness.