Don’t bother, that’s normal /sssssssssssssssssssssssssssssss
Master of Applied Cuntery, Level 7 Misanthrope, and Social Injustice Warrior
Don’t bother, that’s normal /sssssssssssssssssssssssssssssss
My two cents: Yes, it’s bad. The biggest hurdle to people not “intimately familiar” with their distro is A) what it’s using for DNS configuration and B) realizing that there are so many different ways in different distributions, and sometimes within one distribution, that you have to be very careful what googled results you follow. That many browsers do their own thing doesn’t help. I think the best way to solve it would be some desktop level abstraction like PackageKit where it doesn’t really matter what services does the resolving under the hood.
Same with Dolphin. It can even remember credentials in a safe manner in KWallet.
It’ll likely go away with an update. But you can always check xsession log, dmesg, etc to see if there’s a hint on why the screen locking process is crashing.
I have a different Brother MFC printer, but one thing which took me a while to figure out was, that the drivers required the 32 bit version of libc6.
I got a lot wrong initially reading that blog post (updated my comment accordingly). Though, I can sympathize with what he’s saying in that screenshot specifically. If I did maintain a popular open source project I’d rather completdly remove the social aspect than try and manage it.
Looks like I didn’t understood what I read. I should have paid more attention.
[…] the lead dev seems to be a fucking idiot.
How so? I mean, I am tempted to agree. Reaching out to that unofficial community to improve their conduct instead of just ignoring them is pretty idiotic. But, are you sure you’ve read the linked page and understood its content?
I didn’t pay attention when reading the linked page. Its author is/was the creator of wlroots, not hyprland. He reached out to the lead dev of hyprland which is very much associated with the discord community. I got so much wrong reading that …
Sorry for being contrarian.
Well, we live in a democracy: 9 out of 10 people enjoy bullying or don’t care about it. If you hate democracy, go to North Korea, snowflake!
(obvious /s is obvious)
In other non-news: Using a software doesn’t require visiting a loosely associated unofficial community. This has strong vibes of people wanting to be Christian and changing Christianity while being opposed to ~half the bible’s content if they bothered to read it. Just fuck that cesspool and move on with your life …
There is a distinction between regular updates and distribution upgrades. The latter have to be done manually. I know that distribution upgrades via GUI have been in the works; no idea if that is a thing yet.
https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-new-release/
As for what’s missing: The most important thing to keep in mind is that fedora releases only get security updates for 1 year after release + some grace period depending on the date of the n+2 release.
Don’t.
What people here are saying: Don’t try to enter the dimension of suffering and pain.
What you are saying: OK. How can I enter the dimension of suffering and pain?
If you insist on entering the dimension of suffering and pain: Go a step further back and develop your game for DOS. Older Windows versions will just be able to run it out of the box, and everything else can run it via DOSBox.
I think using OpenGL will be even harder than DX8. Your point with the documentation is spot on: it will be hard to come by. As for TLS/SSL third party libs: I had the fun opportunity to implement/maintain the backwards compatibility for a piece of software for Win XP/Server 2003 ~3 years ago. We had to jump some hoops with a custom compilation of OpenSSL to get the parts of TLS 1.2 we needed in Windows 10. I can say with confidence, that that route is a dead end for even older Windows versions.
Thanks Captain Obvious.
Little add-on: My gut feeling is that you’ll need to set up a development environment on Windows 98/Me or NT4/2k, maybe XP.
If you use plain C and only the part of the Win32 API that has been availlable since 95 that should be doable. No modern toolkit/SDK will likely enable you to do that. The problem will be finding downloads/sources for OS, SDK, and IDE old enough to target Windows 95. You might be able to use DirectX 8, but it will require installing DirectX 9 on newer versions of Windows as a dependency (DX10+ is not backwards compatible with DX8 and DX8 is the latest you get for Windows 95, DX9 is still availlable for Windows 11). Your game will have to be offline only or rely on insecure network stack because hardware old enough to run 95 does not have CPU instruction sets required by implementations for modern SSL.
would this greatly affect the development process at all?
Well, take the information I provided and have a guess ;-)
malicious Debian package repository
*laughs in RPM*
This comment was presented by the fedora gang.
To be fair, that’s also true when running natively under Windows.