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 seriously wonderful news. DLSS was just head and shoulders above FSR 2 in my experience, so if this comes close it's a huge deal. DLSS is (hopefully was) Nvidia's biggest advantage over AMD in my opinion.

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 droped, 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!

I'm only an armchair physicist, but I believe this isn't possible due to relativity. I know that, at least, there are cases where two observers can disagree on whether an event occurred simultaneously. Besides all the other relativity weirdness, that alone seems to preclude a truly universal time standard. I would love for someone smarter than me to explain more and/or correct me though!

You're looking for Fred Rogers, more commonly Mr. Rogers. He was the host of the popular children's show Mister Rogers' Neighborhood, and is revered for having been incredibly compassionate both in public and private.

If anybody's curious, I tried it with GPT4 and it got it right.

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.

Yeah personally I haven't needed jQuery in years.

Having made the choice to use GTK for a Rust project years ago - before a lot of the more Rust-friendly frameworks were around - this is exactly why I chose it. Nothing to do with DEs or any of that, just looking for a better coding experience. Now I'd probably choose one of the several Rust-focused solutions that have popped up though.

I mean yeah, we should absolutely be replacing as much fossil fuel use as we can with existing renewable energy tech. But there's no reason we shouldn't also be investing in fusion research, at least as far as I'm aware

Typically this thinking is mostly correct - e.g. Manifest v3 - but not in this case. If websites see enough users using chormium, via user agent or other fingerprinting, they'll be more willing to require WEI. And unlike Manifest v3 etc. this affects the whole web, not just users of one browser or the other.

In every case monopolies are bad. Including in tech.