Doo doo, doo doo doo doo doo doo, rii tii tii tiiiii

I could be wrong, but I’m pretty sure Nvidia has patched them into the GTX series, they’re just really slow compared to RTX cards.

You don’t have to save your files to Adobe cloud, if that’s what you mean. It does check for a valid license occasionally, but I’ve used Photoshop when my internet was out without any problems in the past.

“Instructions” is probably the wrong word here (I was mostly trying to dumb it down for people who aren’t familiar with graphics rendering terminology).

Here’s a link to the Digital Foundry video I was talking about (didn’t realized they made like 5 videos for Alan Wake 2, took a bit to find it).

The big thing, in Alan Wake 2’s case, is that it uses Mesh Shaders. The video I linked above goes into it at around the 3:38 mark.

AMD has a pretty detailed article on how they work here.

This /r/GameDev post here has some devs explaining why it’s useful in a more accessible manner.

The idea is that it allows offloading more work to the GPU in ways that are much better performance-wise. It just requires that the hardware actually support it, which is why you basically need an RTX card for Alan Wake 2 (or whichever AMD GPU supports Mesh Shaders, I’m not as familiar with their cards).

There’s kind of a difference between “we scraped the internet and decided to use copyrighted content anyways because we decided to interpret copyright law as not being applicable to the content we generate using copyrighted content” (omegalul) and “we explicitly agreed to a legally-binding contract with Apple stating we won’t do that”.

Edit: Here’s another comment I made with links and more information on why this is going to be more common going forward. There’s a very real and technical reason for using these new rendering strategies and it’s why we’ll start seeing more and more games require at least an RTX series card.

You’re misunderstanding the issue. As much as “RTX OFF, RTX ON” is a meme, the RTX series of cards genuinely introduced improvements to rendering techniques that were previously impossible to pull-off with acceptable performance, and more and more games are making use of them.

Alan Wake 2 is a great example of this. The game runs like ass on 1080tis on low because the 1080ti is physically incapable of performing the kind of rendering instructions they’re using without a massive performance hit. Meanwhile, the RTX 2000 series cards are perfectly capable of doing it. Digital Foundry’s Alan Wake 2 review goes a bit more in depth about it, it’s worth a watch.

If you aren’t going to play anything that came out after 2023, you’re probably going to be fine with a 1080ti, because it was a great card, but we’re definitely hitting the point where technology is moving to different rendering standards that it doesn’t handle as well.

only to realize the issue wasn’t the tech

To be fair, electronic whiteboards are some of the jankiest piles of trash I’ve ever had to use. I swear to God you need to re-calibrate them every 5 minutes.

Photoshop does a lot of things in really stupid, convoluted ways. Krita also does a lot of the same things in equally stupid, convoluted ways, but different than PS so you get no benefit from knowing how its done in other software. Text editing comes to mind. Both PS and Krita feel like they were designed by drunk people when it comes to doing anything beyond writing text and picking a font/color/size.

> Thinking the TIOBE Index is worth anything beyond the 2000s.

Meh, potato poboom-

Uhm, yes? Kill codes are dumb. Use a dead man’s switch instead. If you don’t enter the code it self destructs. Now that’s privacy!

Nothing concrete from what I can tell. Becoming a hard fork is relatively recent though (mid-November of last year, roughly).

As a side note, I understand why Gitea and Forgejo went for a “copy GitHub Actions” approach to their CI, but man do I wish more self-hosted repo software tried to copy Drone/Woodpecker instead. Iterative containers in the pipeline is such a smoother build experience, and it kind of sucks that Gitness is the only one doing it (that I know of).

They were still pulling in mainline Gitea changes while introducing their own stuff last I checked.

Also issues with links that get ads on top of them. You can still click them, you’ll get redirected to a blank page (because the ad gets DNS blocked), but with an adblocker you would’ve gone to the non-ad link.

Whenever someone brings this up, someone also brings up the fact that ads are proven to work in general not on everyone. So I guess it’s my turn today.

It’ll just get ignored. I saw a fucking padding: 0.0.3rem at work today, and it just broke the one class.

To be fair, the left images are from Halo 2 and the ones on the right are from Halo 1, so this exact screengrab wouldn’t really be possible to begin with. I’m pretty sure the “doom” meme is a really old Tumblr shitpost that got reposted with different IP/screengrabs over the years (and the RvB one became the popular version?).

The whole Bloodgulch chronicles are forever etched into my mind.

“It’s a sniper rifle, asshole. It’s is a long-range weapon.”

“What were you gonna do: mail him the bullets?!”

It’s not that we want to ignore warnings.

Speak for yourself, I promise you the team I work on actively ignores warnings and doesn’t even want to solve them as they pop-up. Being told you can’t compare doubles (because of precision loss) and ignoring it is on the developer and isn’t even that hard to fix. Most of our warnings come from shit like that.

Like, I get it. It’s probably not worth it to hunt down every “unused variable” warning (especially in an API where we used to have a variable for it and we don’t use it anymore and we don’t want to break the existing API so we just leave it there), but there’s things that are just trivial to fix when you’re working on code that’s right next to it.

Oh yeah, I’m genuinely about to hand-in my resignation as soon as I find another job over this kind of shit. I keep being told that the business is really trying to clean-up its act when it comes to coding practices, but they keep putting some of the most incompetent people I’ve ever worked with in charge of shit (because they do promotions based on years of experience instead of actual actionable experience). It’s awful.