mox

joined 1 year ago
[–] mox@lemmy.sdf.org 1 points 5 hours ago

Mainly, there's a good chance Jacob will have progressed the x86_64 backend far enough that we can enable it by default for Debug mode on ELF targets.

That sounds a lot like self-hosted code generation. I wonder if this is a significant step toward bringing async back to Zig.

For the relevance, see the FAQ:

https://github.com/ziglang/zig/wiki/FAQ#what-is-the-status-of-async-in-zig

Note especially the last three bullet points.

[–] mox@lemmy.sdf.org 7 points 6 hours ago (2 children)

John Crichton... are you still out there?

[–] mox@lemmy.sdf.org 16 points 6 hours ago

non-unixlike

Linux-based

Sorry, friend, but you'll have to pick one. Linux is Unix-like.

[–] mox@lemmy.sdf.org 8 points 8 hours ago* (last edited 6 hours ago)

That build should handle 1440p gaming for more than a few years to come.

You might want to consider swapping out the Ryzen 7 7700X for an X3D model. Many games get a significant boost from the extra cache. It can also make game performance less dependent on your RAM speed.

Maybe wait until the upcoming hardware releases hit the market, because those can drive down the prices of the stuff you intend to buy.

[–] mox@lemmy.sdf.org 3 points 8 hours ago

I don't know of any generic controllers, and wouldn't trust them to have consistent hardware between production runs. All the worthwhile controllers I've used have brand names. Having said that...

Logitech makes decent, affordable, basic controllers. My only complaint about the F310 / F710 is that the analog stick dead zones are a little bigger than I like. (Maybe I'm just spoiled by Sony models, though.)

Sony's DualShock 4 v2 and DualSense are great in my experience, and not terribly expensive when they go on sale.

[–] mox@lemmy.sdf.org 5 points 8 hours ago* (last edited 3 hours ago)

You might find it interesting to know that the Atari 2600, Commodore 64, and Nintendo Entertainment System (aka Famicom) all used variants of the MOS Technology 6502 CPU. (The bottom of the Computers and games section on that page pictures more devices that used it.)

I expect this is part of why so many games were ported between those systems, even at a time when most games were written in (non-portable) assembly code. These machines all support the same CPU instructions.

[–] mox@lemmy.sdf.org 9 points 8 hours ago (5 children)

I hope they manage to get it complete, and good. Giving Oblivion another try (this time exploring the rest of the world instead of focusing on the boring main quest) has been on my list for a while, and improved graphics would be welcome.

That font, though... not a good choice for quickly delivering information. Mods to the rescue?

 
  • Fix Proton integration bugs so Proton-fixes are applied
  • Do not offer DXVK, VKD3D, D3D Extras or DDXVK-NVAPI on Proton versions; Proton will handle these.
  • The "Enable Esync" and "Enable Fsync" settings are now passed on to Proton
  • DXVK's integrated D8VK will be enabled in Proton
  • Emulator BIOS file location (used by libretro) may be set in Preferences
  • Obtain the release year from GOG and Itch.io.
  • MAME Machine setting uses a searchable entry for its enourmous list
  • Support for importing Commodore 64 ROMs
[–] mox@lemmy.sdf.org 3 points 1 day ago* (last edited 1 day ago)

Blizzard games have always run very well in Wine.

They run, but I wouldn't say very well. A few counterexamples off the top of my head:

  • Wine raw input patches are required to avoid subtle mouse glitches in Overwatch.
  • Saving Overwatch highlight videos doesn't work.
  • Battle.net launcher changes have made it unusable in Wine more than once, leaving people suddenly unable to play for days or weeks even when the games themselves would run fine if they could be updated and launched.

You might not notice the problems (or not as often) if using Proton. That's because Proton includes a load of Wine patches for stuff like this.

It would be nice if Blizzard tested on Wine and worked with the maintainers to ensure things stayed smooth.

[–] mox@lemmy.sdf.org 11 points 2 days ago* (last edited 2 days ago) (2 children)

More like, "don't pick an inflammatory minor excerpt to represent a lengthy and well-reasoned post."

Similarly, don't choose a red fruit to represent a pine forest just because there happens to be an apple tree somewhere within. It's misleading.

[–] mox@lemmy.sdf.org 2 points 2 days ago

The thumbnail reminds me of that Wheee! Internet Explorer vs Firefox video.

 

Having the recipes posted in text would:

  • Make it easy for readers to copy them for later use, instead of having to manually transcribe them
  • Improve accessibility for the vision-impaired
  • Ensure that the recipes remain visible months or years later, surviving image cache and file host purges
  • Make them visible to folks on instances that don't cache remote media, without having to allow off-site images in their browsers (which can be abused for web tracking)

Should this be a rule?

view more: next ›