@PurpCat > dealing with yet another layer of extra fuckery I agree, that throwing Wine or whatever they have like that these days, Proton and whatnot, into the mix does add another layer of complexity, but examining Wine's logs at least makes sense if you want to figure out why something doesn't work, with Windows it's: "Deal with it, it just doesn't — get another game". I can show you my numerous attempts at contacting EA or UbiSoft support — they literally never go beyond "Update you videocard drivers", they are never able to help you with something more complex than their textbook set of issues. Therefore my original point is that is you want a completely effortless experience, consoles are the way to go. PC master race style remarks that you just have to get yourself a good rig are a load of crap IMO — some features of top of the line hardware never get utilized outsize of tech demos, developers seldomly care enough to even optimize for that because most of their customers use high to medium settings anyway, never ultra . You spend $20k on latest-greatest only to discover more bugs that you never encounter with lower settings and feel yourself fucked over. In most of the cases with PC gaming you get exactly the same experience as with consoles, but with more fuckery. Of course not all genres are suitable to be played with a controller, but come on — even indie shit is already on there. Another problem is dealing with insane amounts of DRM bullcrap, with Windows you're only knee-deep in this shit, not all the way, but even this changes for the worse too. And fast! :marseysigh: @mischievoustomato@sneeden@arcanicanis
@arcanicanis I agree, we are unlikely to see truly native games, in a sense that Quake games were, ever again. Even if it's not some smartass wrapper around Windows build, like Proton, the devs most often rely on what their engine of choice offers, if it supports the platform — have a build, if it doesn't, then well… life's unfair. In terms of reliability it's a mixed bad too: if you're on some popular platform, bugs will likely get fixed, if it's something less common and platform specific — original devs just don't care most of the time. I'm fine with containerization though. GOG also uses something like that — their wrapper is a set of old libraries and scripts that LD_PROLOAD them in a nice way. I don't mind having redundant copies of libraries as I have to rely on glibc chroot for these things anyway — most of my systems are musl-based. @mischievoustomato@PurpCat@sneeden
@PurpCat@mischievoustomato@sneeden@arcanicanis Because that is what you do if you want games to "just work". In fact, gaming on Windows involves insane amount of fuckage, PC gamers just got used to it. If your config is even a tiny bit non-standard, good luck figuring out why it doesn't work. There are many games that refuse to launch just because you didn't install them to c: drive, and they don't even give you any meaningful error messages, they just don't run. Support can't figure out shit most of the time too, best luck if someone on some fucking forum has managed to figure out why shit doesn't work as expected.
@p I'd switch to OpenBSD myself, but to me it looks like hardware support for literally anything is literally non-existent there. I'd still like to be able to use my computer for things other than tinkering with my computer, like you know, having hardware video decoding and output support so I can at least watch some movies not from 35mm film — just like absolute most of people living in 2023 do. Having some basic Bluetooth support would also be nice, so at least a fucking mouse could work :marseylaugh: As much as I absolutely despise linux and consider it complete and utter garbage, there are no real alternatives. You can't even cut back on modern stuff and live your life the way you did in the 90-ies — you can only pretend. As in the nineties I could go outside and buy music on CD at a nearest newspaper stand — I can't do that anymore. Whether we like it or not, things are different now. As for Wayland — unlike systemd or this pulse-shit I have zero problems with it. I know that somewhere deep down it's all messy from software design perspective. But I have zero nostalgia for X11 either — it's not new, but it had accumulated a lot of legacy garbage throughout literally decades. So for me one is a piece of shit and the other one is also a piece of shit — but both get things done to an extent. I have old ThinkPads unable use Wayland and I use Xorg on them and I have a couple of more recent laptops that use Wayland — and I really like using them, "every frame is perfect" isn't bullshit in the slightest, I really like how buttery smooth everything is, I really like the straightforward way of controlling multiple outputs Sway gives me, scaling looks good, everything looks good. And it's not resource hungry at all, machines are 98% idle and most of RAM is used for filesystem cache. It's not perfect — acceptable. And despite all this, I can totally get that for some it doesn't come even close to that — buggy hardware support is no joke, but I don't get throwing shit at it just because it doesn't work for you in particular and making it look as if something is fundamentally wrong with it — it isn't and for some it just works. I'm not encouraging anyone to use Wayland if it implies dealing with broken hardware support, but I never encourage anyone to keep using X11 either — why? Just because this shit is old? It doesn't make any sense :marseyshrug: @dcc@threat@sjw@ins0mniak@mia@sysrq@MK2boogaloo@jeff@SuperSnekFriend@rher@meso
@p > Wayland sucks, and not in a "deep down it's a mess" sense, it sucks in the sense that it breaks my shit, way up here on the surface: things I do will no longer work. I don't like X, but X does the things I want it to do. That's the point. For me Wayland does things — the whole story behind me switching to Wayland on some of my computers had been something like me noticing horrible tearing when scrolling pages in Firefox. And I've been thinking to myself: "Hey, this isn't a 20 year old ThinkPad, this shouldn't be like that",— so I went looking online how to solve this shit and I came across the whole Wayland thing and every frame being perfect, and as I've been on dwm, I started looking something similar and found Sway — it took some time to configure everything the way I like, but since then I just worked. Some things got different, but no tearing. > "Wayland is newer and thus inevitable" is the worst possible way to think of it But for me it's nothing of this sort — I didn't go Wayland because some article online claimed that it's great, I also didn't do it because my distro switched to it — nothing of the sort. My distro was and is Void nearly universally, Wayland solved the only problem for me that is was supposed to solve — that's why I kept it, no other reason. Nothing about it being inevitable, the next big thing, I didn't even know how much it's being despised until I arrived on Fedi, I didn't know who Drew DeVault is. It just got shit done for me — that's it, no ideology bits. > This was a thread about post-apocalyptic desert island cyberdeck Oh, fuck, it IS a different thread! :marseyshock: I went to bed when that OS/2-tracksuit thread was still current and when I woke up, you kept going in this one, and I didn't have a slightest idea that it's a different one. I've been fairly confident that it's just a topic switch — the usual. :marseylaughwith: Well then, sorry for offtopic :marseywink:
@ins0mniak > few tweaks > shit for Go Vim-Go brings a few dozens of Go modules in when you do :GoInstallBinaries though :marseylaughwith: Even some CI shit that I don't think I ever use.
@p I have an olde ThinkPad T40 with only 512 Mbs RAM and it doesn't take Google Chrome to put it to its knees, surf gets the job done just fine. Surprisingly, another machine with half a gigabyte of RAM I have — a slightly less old ARM netbook, subjectively feels a little more nimble, and it doesn't even have a swap file, except for the zramswap trick, probably because unlike ThinkPad it's dual core — but honestly, I don't get how that might improve things. Both machines are still useful with TUI software, like gomuks for Matrix and tut for Fedi, and of course I use w3m whenever I can, but sometimes you just need some web shit and I'm not even talking about JS-heavy stuff, even basic stuff that embeddable WebKit in surf can do migth eat up lots of RAM.
@sun_eater Never listen to tech-related advice on Fedi! These people here are complete nutjobs, they use protocols from the last century and find it funny 🤪
@kirby Well, I don't really know it, but I did fix a couple of things in Pemorla for my instance — in most cases the code looks pretty straightforward to me, especially when it's stuff like MRF. There is nothing in this one that looks specific to old version, I think it should work.
@kirby They see them as start even if it's something retarded like wrench or raised eyebrow… TBH I miss that feature which was lack of thereof. Sometimes I have to open PleromaFE or Tusky only to discover that this "pleroma_emoji_react" is in fact something retarded like a raised eyebrow emoji or a wrench :marseysigh: