Quoting: F.Ultra

Quoting: JordanPlayz158

Quoting: minidouI fail to see how glibc devs could be blamed for removing a function deprecated for 17 years (though I can agree a major version bump should have been called for). Do videogame devs need that much nursing ? EAC linux lib is a recent piece of software, how many deprecated dependencies do they use ?

Quoting: TermyI tend to agree with the criticism about unstable APIs for many cases - but in this case, i really blame Epic for using a function deprecated for almost two decades in a recent piece of software.

From everything I've read from other people, it wasn't obvious that the function was depreciated. You shouldn't need to search up, "is x function depreciated glibc" for every function you use, it should be immediately obvious (like most languages I know have comments or a depreciation tag), some say that all distros somehow knew about this but you shouldn't need to be familiar with linux development or need to be in the right communities to know about a depreciated function.

Small nitpick here, but DT_HASH is not a libc function, it's a linker section in the ELF header of a shared object. The function that utilizes this section is dlopen() and that function have not changed and it works, it's only applications that tries to read the ELF data manually that have to handle DT_HASH and DT_GNU_HASH, and by all means it looks like the glibc devs "incorrectly" thought that dlopen was their ABI/API and not the actual linker section in the ELF headers.

Thank you for correcting the information, I am not a C developer nor have made linux applications "natively" so thank you for clearing that up

View this comment - View article - View full comments

Quoting: ShabbyXIt's made exactly so that libraries *can* break ABI if they have to, without the world imploding. glibc made a breaking change, and no matter how small, they should have made an incompatible version change. Yes that would still be inconvenient, but at least it's detectable and fixable. Imagine if python3 did all its backward incompatible things but still called itself python2.

Yes, that's exactly the point we were making, they didn't treat it as a breaking change as they just incremented the patch number by 1 rather than the major. Not to mention a lot of people have said it wasn't very clear and I could buy that as documentation doesn't seem to be a strong point in either linux or c in general (or I could be wrong (or xdg-desktop-portal could be a bad example of a c library) but when I attempted to make an application using xdg-desktop-portal they had the equivalent of a javadoc but that was about it, there are no examples provided in the repo for how to use any of the objects (or it wasn't clearly labeled or findable), there were no tutorials online and I looked into other repos (that are flatpaks as they must use xdg-desktop-portal to my knowledge) and it was a mess because different applications use different languages or sometimes used a middle man library or some combination of the two which made it difficult to know how to use the interface)

View this comment - View article - View full comments

Quoting: minidouI fail to see how glibc devs could be blamed for removing a function deprecated for 17 years (though I can agree a major version bump should have been called for). Do videogame devs need that much nursing ? EAC linux lib is a recent piece of software, how many deprecated dependencies do they use ?

Quoting: TermyI tend to agree with the criticism about unstable APIs for many cases - but in this case, i really blame Epic for using a function deprecated for almost two decades in a recent piece of software.

From everything I've read from other people, it wasn't obvious that the function was depreciated. You shouldn't need to search up, "is x function depreciated glibc" for every function you use, it should be immediately obvious (like most languages I know have comments or a depreciation tag), some say that all distros somehow knew about this but you shouldn't need to be familiar with linux development or need to be in the right communities to know about a depreciated function.

View this comment - View article - View full comments

Quoting: const

Quoting: RustyTo be fair to glibc, this is a problem on the part of Epic using the deprecated DT_HASH instead of DT_GNU_HASH. EAC's Linux implementation is frustratingly half-baked. It really feels like Epic is the biggest barrier to gaming on Linux now.

Question is: why does glibc constantly break the API(/ABI)? It's a damn c library and should be backwards compatible. If at all, functions should be altered on major releases, so distributions have a chance to handle such stuff. Couldn't they just have redirected that damn call? It's really infuriating they don't care for backwards compatibility at all and this hurts linux in many ways.

Yeah also I've heard from some sources that they never officially depreciated it so no devs knew it was depreciated until it was removed from glibc entirely. In which case, it might not have been on epic but rather on glibc.

View this comment - View article - View full comments

Quoting: natis1Apparently it can be exploited by letting you add fake messages to make the other person look worse. Here's a proof of concept: github.com/nodusclient/gaslight [External Link]

I thought this was game dev 101 to not trust the client? What has microsoft done to mojangs dev team to allow for such flaws

View this comment - View article - View full comments

Quoting: Liam Dawe

Quoting: JordanPlayz158

Quoting: pedrobaezaYes, I have been moved up to Q3!

:( I was in Q3 but moved to Q4 lol, guess it goes both ways

No, you would have been in Q3 or later, no one has been delayed.

Ah yeah, that makes sense then.

View this comment - View article - View full comments

Quoting: pedrobaezaYes, I have been moved up to Q3!

:( I was in Q3 but moved to Q4 lol, guess it goes both ways

View this comment - View article - View full comments

Plus, they explained that every month "thousands" of people have their accounts stolen due to these modified clients. So it is a big issue

So let me get this right, they have an issue with either their servers or client that permits someone with a mod to be able to seemingly steal login credentials and rather than fix the underlying problem, they decide the much more rational solution is to add an anticheat..... WHAT?

View this comment - View article - View full comments