They have concepts of an ICBM.
They have concepts of an ICBM.
Kessler syndrome isn’t really that much of a risk specifically with Starlink (for now at least), as SpaceX seems to be doing things right despite Musk. They’re in such low orbits that even with a catastrophic loss of control, they’ll deorbit very quickly. The real risk comes as more companies and countries try to get a piece of the megaconstellation pie. Starlink in its own seems to be fairly safe and sustainable on its own, but that may quickly change when communication for collision avoidance maneuvers needs to be international.
Despite Musk’s well-earned reputation for being a shithead, SpaceX has this far been doing the right thing far more often than most other space companies, and while it’s certainly possible that will change, the Starlink constellation will entirely disappear very quickly without constant replenishment, so it’s not as if we’d have no chance to act if they begin to show signs of concerning behavior. What’s far more worrying to me in terms of Kessler syndrome is the recent escalation around space warfare, as tensions between Russia, China, and the US continue to boil and nobody seems willing to really commit to making space a neutral zone. Even with space historically being an area of strong international cooperation despite politics (just look at the ISS), that unfortunately seems to be rapidly changing.
Well they said .NET Framework, and I also wouldn’t be surprised if they more or less wrapped that up - .NET Framework specifically means the old implementation of the CLR, and it’s been pretty much superseded by an implementation just called .NET, formerly known as .NET Core (definitely not confusing at all, thanks Microsoft). .NET Framework was only written for Windows, hence the need for Mono/Xamarin on other platforms. In contrast, .NET is cross-platform by default.
Holy shit. I knew they were going to simplify Raptor a lot, but even knowing most of the rat’s nest was sensors/etc., this is insane. I wish we could see cross sections!
I’m worried it’s a lithography issue. The recent GamersNexus and Level1Techs coverage seems to point that way, at least to me. For example, they mention CPUs working fine for a while, then suddenly becoming increasingly unstable. There’s so much that can go wrong with lithography that could cause that kind of behavior, and we know they’ve been having issues given the whole 14nm debacle.
Honestly, after DOS2, I’d play a Larian game in any setting just based on them being the devs - and that goes double after BG3. Their handle on storytelling and environments is so good I’d trust it would be enjoyable even in a setting I’m not interested in.
I’ve found it depends a lot on the game. In CP2077, DLSS+frame gen looks great to me with full raytracing enabled. But in The Witcher 3, I found frame gen to cause a lot of artifacts, and in PvP games I wouldn’t use regular DLSS/FSR. In general I’ve found the quality preset in DLSS to be mostly indistinguishable from native on 3440x1440, and I’m excited to try FSR 3 when I get the chance.
I’ve got the same results by just asking it to repeat the system prompt.
This is a use-after-free, which should be impossible in safe Rust due to the borrow checker. The only way for this to happen would be incorrect unsafe code (still possible, but dramatically reduced code surface to worry about) or a compiler bug. To allocate heap space in safe Rust, you have to use types provided by the language like Box
, Rc
, Vec
, etc. To free that space (in Rust terminology, dropping it by using drop()
or letting it go out of scope) you must be the owner of it and there may be current borrows (i.e. no references may exist). Once the variable is drop
ed, the variable is dead so accessing it is a compiler error, and the compiler/std handles freeing the memory.
There’s some extra semantics to some of that but that’s pretty much it. These kind of memory bugs are basically Rust’s raison d’etre - it’s been carefully designed to make most memory bugs impossible without using unsafe
. If you’d like more information I’d be happy to provide!
That’s the point. Malicious compliance.
As spacecraft reenter the atmosphere from orbital speeds, they’re going so fast that the atmosphere is compressed enough (and so gets hot enough) to free the electrons from the atoms in the air. This forms plasma. The special thing here is that we got live video during this portion of reentry; the free electrons in plasma heavily interfere with radio communications, so in previous missions there has been a full communications blackout at that time. Starship did not experience that blackout, which is unique. I’m not qualified to say exactly why, but the team was stressing that Starship is big enough that it “punches a hole through the atmosphere”. Another factor could be the 4(?) starlink terminals on the leeward side providing redundant communications signals.
Even as an (older) zoomer in the US, this was never a thing for me. No one cared what phone you used. If you had an Android you wouldn’t be in iMessage group chats but no one judged you for it.
The issue is that, in the function passed to reduce
, you’re adding each object directly to the accumulator rather than to its intended parent. These are the problem lines:
if (index == array.length - 1) {
accumulator[val] = value;
} else if (!accumulator.hasOwnProperty(val)) {
accumulator[val] = {}; // update the accumulator object
}
There’s no pretty way (that I can think of at least) to do what you want using methods like reduce
in vanilla JS, so I’d suggest using a for loop instead - especially if you’re new to programming. Something along these lines (not written to be actual code, just to give you an idea):
let curr = settings;
const split = url.split("/");
for (let i = 0; i < split.length: i++) {
const val = split[i];
if (i != split.length-1) {
//add a check to see if curr[val] exists
let next = {};
curr[val] = next;
curr = next;
}
//add else branch
}
It’s missing some things, but the important part is there - every time we move one level deeper in the URL, we update curr
so that we keep our place instead of always adding to the top level.
If anybody’s curious, I tried it with GPT4 and it got it right.
The GPU I used is actually a 1080, with a (rapidly declining in usefulness) Intel 4690k. But I suppose laptop vs desktop can certainly make all the difference. What I really want is GPU virtualization, which I’ve heard AMD supports, but I’m not about to buy a new GPU when what I’ve got works fine.
My experience with single GPU passthrough on Proxmox to a media VM was pretty positive, especially for it being an old Nvidia card. Even as someone doing it for the first time, it just took about 10 minutes to figure out the passthrough itself and another ~15 to figure out some driver issues. And it’s worked perfectly since then. All in all much better than what I’d expected.
Besides rendering bugs that may or may not be Safari’s fault, I wanted to get uBlock Origin on an iPhone but it’s not available, IIRC because the content blocking API is more restrictive than what uBlock is designed for.
They’re welcome to retaliate. They’re just not allowed to indiscriminately bomb civillian infrastructure.
Here’s a field manual that details the rules and has some advice. There are a whole host of rules protecting civillians hospitals, but in the case where Hamas is using them as military bases, I’d say they can be considered primarily as human shields, though I’m no expert, and even if that’s not the case they’re still civillians and therefore protected. According to paragraph 2-20, “feasible precautions” must be taken to reduce civillian harm. This means bombing is pretty much out of the question, but there are still plenty of other ways to get at Hamas, such as SpecOps, sieges, and diplomacy. It’s a difficult situation, but that doesn’t mean you get to kill civillians with impunity.
Bevy, cause I’m a sucker for Rust