Willem

joined 1 year ago
[–] Willem@kutsuya.dev 11 points 10 months ago

Full 32 bit on 64 bit Unix support is a big thing in my opinion, even though most people won't notice it (as an "extra" this also will allow running 32bit games on osx games and proper wine support on arm64 devices like your phone).

Also the additions to directshow will get more (older) games working properly.

From what I read this was some great work in the foundation of wine and hopefully accelerate their work even more.

[–] Willem@kutsuya.dev 31 points 10 months ago (1 children)

Also the reliable income makes them more credit worthy, allowing greater loans from banks and making it possible to grow more.

Tbh it only sucks for the customers

[–] Willem@kutsuya.dev 7 points 10 months ago (10 children)

The biggest feature of Wayland for me is mixed refreshrate monitors works OOB. On X this is a pain to get even remotely working and it's impossible if your monitors aren't dividable (120/60 works, 144/60 stutters).

This is from my experience something that is starting to be a way more common issue (high refreshrate laptops with 60 external monitors at businesses or high refreshrate monitor for gaming and a smaller secondary monitor for info lookup/discord).

other than that, Xorg does win the "more stable" prize for me, but if I wanted stability, I should've become a carpenter.

[–] Willem@kutsuya.dev 7 points 11 months ago

It's quite a bad UX, but generally error 2 from make means the called program resulted into an error.

Usually this is accompanied with another error somewhere up the log. Multiple cores can make this a challenge to scan the log for however, so maybe try compiling without the -j argument, that should get the actual error closer to the end.

From my experience, it's usually an outdated config for the kernel (like using a config for 5.1 while compiling 6.7) or a missing dependency. However the real error will be somewhere among the logs, who knows, maybe it's a missing processor instruction (it's really bad UX).

[–] Willem@kutsuya.dev 1 points 11 months ago

sounds to me like a timing issue. By using the proton log you might slow down to the point the timing issue doesn't give you problems anymore. Try disabling vsync and enabling a fps limit (warframe has both settings itself).

Another possible cause could be filesystem going to a powersaving mode during normal gameplay and by writing logs you keep the disk in high performance.

[–] Willem@kutsuya.dev 3 points 1 year ago

yes, those two "autofixes" are "fixed" now. (it's a opt-in setting)

[–] Willem@kutsuya.dev 41 points 1 year ago (6 children)

Python is soon to be integrated into excel, I might not be a python fan but if it's gonna replace vba I'm all for it.

[–] Willem@kutsuya.dev 3 points 1 year ago (1 children)

I use a single gpu that I detach from my host and reattach in a vm when I start the vm (and vice versa). I don’t think windows will enjoy a sudden lack of gpu.

[–] Willem@kutsuya.dev 4 points 1 year ago

Like a lot of people already mentioned, it’s because of hardware driver’s mostly. But let’s not forget Microsoft has this figured out mostly already, since pretty much all drivers that have a version for Vista 64bit (2006) works on Windows 11.

Android is catching up a bit though, they split the update process and you now receive security updates almost directly from google since Android 10.

[–] Willem@kutsuya.dev 5 points 1 year ago (1 children)

I use Trilium, it just scratched the need I had which obsidian and logseq couldn't somehow.

view more: ‹ prev next ›