Quoting: scaineI honestly wouldn't have minded just "Pop", but Pop!_OS is just crass.

They could have tried to fit a # or a smiley face in there, too. My brain just immediately replaces whatever it is with simply "Pop" anyway. Although now I'm gonna be thinking of them as the po-po.

Quoting: scaineGoogling Pop!_OS issues is fun too - google ignores the !_ and you often find references to "popos" which is an old blighty nickname for the police (apparently now popular in Hong Kong too).

"This real hip-hop
And it don't stop 'til we get the po-po off the block"

View this comment - View article - View full comments

Quoting: Termyif i recall correctly, it's more about better compatibility with games doing something outside the official windows-system-calls?

No, that's a different thing. It's syscall user dispatch that bounces stray Windows system calls back to Wine for processing.

This one is about adding capabilities to futex that weren't thought of back in 2002 - including some that are in Windows' later implementation, which are used by developers making applications for Windows - without breaking userspace applications that are already using the original futex.

View this comment - View article - View full comments

Quoting: slaapliedje

Quoting: gustavoyaraujoI have 3 Steam Controller and I should say it's an awesome piece of hardware, I hope Valve will keep supporting it to work with Steam.

Same here. The nicest support is when they properly support the Steam Input API. Then it should detect which controller you have, and map the in-game button graphics to correspond to it! One of the most annoying things I encounter in games these days is that they standardize on the Xbox button layout, even if you're using a playstation controller. Not enough developers utilize that though.. :(

That really winds me up. Games generally have a PlayStation port; they've got the assets already, and the means to choose which to display. But... they don't.

View this comment - View article - View full comments

More easily translating Windows' behaviour to Linux was obviously the primary initial motivation, but I don't think it will end up as the only one. Being able to wait for one of many signals seems like the kind of thing that would be generally useful; there's a reason Windows has that function, after all.

View this comment - View article - View full comments

Quoting: Ehvis

Quoting: CatKiller

Quoting: Liam Dawe

Quoting: ElectricPrismImagine we could do for GIMP what has been done for Blender, what an amazing thing that would be.

Will never happen while it's called GIMP.

Unfortunately, the project for GIMP-that's-not-called-GIMP withered on the vine.

It's a obscure non-contextual meaning in one language that is not the native language of most people. You can't expect the general population to care.

I'm not bothered by the name. Sure, stating from the outset that your product is in some way subservient or hobbled isn't the best marketing move, no matter how hilarious the initial devs found it, but whatever. There are other products whose names are gibberish (Tumblr and what-have-you) or way worse (the Toyota Shit, for example).

Liam's right that there are some people that are bothered by the name. Glimpse showed us that there aren't enough people that want to use and improve the Gimp, but are bothered by the name, to make it actually viable.

Personally, I think the non-responsiveness of the Gimp project to the GTK and Python transitions is what's doomed it, way more than the name, and some other project will steadily acquire more advanced functionality and eventually take over that niche entirely.

View this comment - View article - View full comments

Quoting: Liam Dawe

Quoting: ElectricPrismImagine we could do for GIMP what has been done for Blender, what an amazing thing that would be.

Will never happen while it's called GIMP.

Unfortunately, the project for GIMP-that's-not-called-GIMP withered on the vine.

View this comment - View article - View full comments

I think this might bump me onto the Experimental branch. The only game I really use Proton for at the moment is No Man's Sky and - because I use overlays to cap the framerate to compensate for the game's lumpy frame timing - I'd stuck with 5.10 rather than the containerised versions. NMS is getting DLSS, 470 gets DLSS that Wine can use, and Proton Experimental starts using it. Should be interesting to try.

View this comment - View article - View full comments

Quoting: 3zekielBtw, do we have any news on when 470 series is coming ? I am quite hyped now.

The DLSS-in-Proton needs 470, since that includes the dll to be dropped into the Wine prefix, and they said that that was happening this month, so sometime this month. Roughly.

View this comment - View article - View full comments

Quoting: gardotd426This is nonsense and demonstrates that you have no idea what goes into anything to do with vkd3d-proton. And Joshua is a vkd3d-proton *and* DXVK developer, and knows infinitely more about this shit than you do.

In particular, he was involved with the creation of the vendor-neutral Vulkan ray tracing extension, redid Q2RTX to use the vendor-neutral Vulkan ray tracing extension, and... wrote an open source implementation of Vulkan ray tracing for AMD hardware, which AMD have failed to do themselves.

View this comment - View article - View full comments

Quoting: MohandevirIronburg Inventions didn't create back buttons, they just adapted something that was already used elsewhere.

Well, to be fair, an innovative arrangement of existing things is legit patent material, and Valve did try using buttons rather than paddles and found that it wasn't as good.

Oh well... Pattents...:sick:

Yep.

View this comment - View article - View full comments