This isn’t about the play store: it’s about installing anything at all. I couldn’t care less if AI slop is on the play store though to answer your question

These questions are always asked in the opposite direction. What’s right with making devs verify? What does it gain an end user?

Yea that made me laugh; I just updated my resume from LaTeX to typst a few months ago actually

I wouldn’t be surprised if this is actually what happened here… tech companies in general don’t delete data if they can avoid it. I worked for companies that would just set deleted = 1 in the DB on delete calls. Google has more ability than anyone else to put that data to use

The effect they’re talking about comes from the peppercorns, not the peppers. You heat them slightly in a pan and then grind them in a mortar and pestle. I run them through a fine strainer after that, but I dunno if you have to.

What I think though is that it’s particularly hard on Linux to fix programs, especially if you are not a developer (which is always the perspective I try to see things from). Most notable architectural difference here between f.e. Windows and Linux would be how you’re able to simply throw a library into the same folder as the executable on Windows for it to use it (an action every common user can do and fully understand). On Linux you hypothetically can work with LD_PRELOAD, but (assuming someone already wrote a tutorial and points to the file for you to grab) even that already requires more knowledge about some system concepts.

You’re not even realizing how advanced of a user on Windows you have to be to realize that putting a DLL in the correct directory will make that the library used by the program running from that directory. Most users won’t even know what a DLL is. Also I work in security professionally and I’ve used this fun little fact to get remote code execution multiple times, so I don’t see how it’s a good thing, especially when you consider that Linux’s primary use case is servers. You can do the exact same thing on Linux, as you said, it’s just opt in behavior. If you are knowledgeable enough to know what a DLL is and what effects placing one in a given folder have, you’re knowledgeable enough to know what a shared library is and how to open a text editor and type LD_LOAD_PATH or LD_PRELOAD. I don’t buy this argument at all.

Linux Desktop is predominantly a volunteer project. It is not backed by millions of dollars and devs from major corporations like the kernel or base system. It is backed by people who are doing way too much work for free. They likely care about accessibility and people using their project, but they also care about the myriad of other issues that they face for the other 90+% of their user base. Is that hugely unfortunate? Yes, it sucks. I wish there was money invested in Linux as a desktop platform, but compared to macOS and Windows it’s fair to say there is a rounding error towards $0.

This is not semantics at all. You earlier say that Linux not having a stable ABI is the cause of a ton of problems.

This shit is the exact reason Linux doesn’t just have ridiculously bad backwards compatibility but has also alienated literally everyone who isn’t a developer, and why the most stable ABI on Linux is god damn Win32 through Wine.

Android doesn’t make any more Linux ABI guarantees than anyone else: because it’s using the Linux kernel. I can easily compile a program targeting a generic aarch64 with a static musl C and run the binary on Android. So no, it isn’t semantics, it is good proof that you’re not correct in claiming that Linux ABI stability is terrible. Maybe you’re using the term “Linux ABI” more loosely than everyone else, but that’s not “just semantics”, the Linux ABI is a well defined concept and the parts of it that are stable are well defined.

Life is Strange: Before the Storm shipped with native Linux support back in 2017. That was a different era - glibc 2.26 was current, and some developers made the unfortunate choice of linking against internal, undocumented glibc symbols.

The very first line of your blog post that you shared. That has nothing do do with Linux ABI stability, or honestly even glibc ABI stability, if you’re going to use symbols that are explicitly internal you can’t get annoyed when they change…? That’s a terrible example.

Adobe still shipped CS6 until 2017, so it’s 9 years old. That’s not particularly ancient, and it’s backed by… well Adobe. They have a bit of money. [EDIT: https://helpx.adobe.com/creative-suite/kb/cs6-install-instructions.html actually it’s still available on their site so… I wouldn’t expect any issues]

Did you run Total Annihilation through Steam? I found this link https://steamcommunity.com/app/298030/discussions/0/1353742967805047388/ and people even had to modify things that way. It’s very impressive that it runs at all and yes, Windows is most definitely the king of backwards compatibility. Or at least it used to be, I’m happy to know very little about modern Windows, and it’s definitely not backwards compatible with hardware…

The person who wrote the “filtered out comment” was batshit crazy and clearly didn’t even know what they were talking about. “Stable ABIs are what lead to corpo-capital interests infecting every single piece of technology and chaining us to their systems via vendor lock-in” is one of the most nonsense statements I’ve read on Lemmy. I wish I had more downvotes available.

It’s important to remember that the Linux kernel has millions of dollars and full time devs from companies like Google and Microsoft working on it. The Linux Desktop space does not have that. Like at all. Linux Desktop is predominantly a volunteer project. Valve has started putting money into it which is great, but that’s very recent.

Android

Android is Linux! You’re running your decades old software, on Linux. What was the last completely unmaintained binary that you pulled on Windows and ran (with no tweaking) and the last one that failed on Linux?

Why do you keep sharing that link instead of this one? https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-4-wayland-is-growing-up-and-now-we-dont-have-a-choice/ The one where the same person you’ve been posting says clearly people are working on accessibility and things are improving?

Have you considered joining the community and working with it – like the author of the blog that you keep sharing – instead of trying to insult every one who works on it and calling it a disgrace?

Running 20 year old binaries is not the primary use case and it is very manageable if you actually want to do that. I’ve been amazed at some completely ancient programs that I’ve been able to run, but I don’t see any reason a 20 year old binary should “just work”, that kind of support is a bit silly. Instead maybe we should encourage abandonware to not be abandonware? If you’re not going to support your project, and that project is important to people, provide the source. I don’t blame the Linux developers for that kind of thing at all.

devs are often being discouraged from compiling tools in a way that makes them work forever (since that makes the app bigger and potentially consume more memory)

This is simply not true. If you want your program to be a core part of a distribution, yes, you must follow that distribution’s packaging and linking guidelines: I’m not sure what else a dev would expect. There is no requirement that your program be part of a distribution’s core. Dynamic linking isn’t some huge burden holding everyone back and I have absolutely no idea why anyone would pretend it is. If you want to static link go for it? There is literally nothing stopping you.

Linux desktop isn’t actively working against disabled people, don’t be obtuse. There is so much work being done for literally no money by volunteers and they are unable to prioritize accessibility. That’s unfortunate but it’s not some sort of hypocritical alienation. That also has likely very little to do with the Linux kernel ABI stability like you claimed earlier.

But this idea that “finally we have people that want Linux to work” is infuriating. Do you have any idea how much of an uphill battle it has been to just get WiFi working on Linux? That isn’t because the volunteer community is lazy and doesn’t want things to work: that’s because literally every company is hostile to the open source community to the point of sometimes deliberately changing things just to screw us over. The entitlement in that statement is truly infuriating.

My understanding of the linking rules for the GPL is that they’re pretty much always broken and I’m not even sure if they’re believed to be enforceable? I’m far out of my element there. I personally use MPLv2 when I want my project to be “use as you please and, if you change this code, please give your contributions back to the main project”

It should be noted that statically linking against an LGPL library does still come with some constraints. https://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic

You have to provide the source code for the version of the library you’re linking somewhere. So basically if you ship a static linked glibc executable, you need to provide the source code for the glibc part that you included. I think the actual ideal way to distribute it would be to not statically link it and instead deliver a shared library bundled with your application.

EDIT: Statically linking libc is also a big pain in general, for exampled you lose dlopen. It’s best not to statically link it if possible. All other libraries, go for it.

It wouldn’t; glibc is LGPL not GPL. The person you’re replying to was mistaken.

glibc is released under the LGPL, not the GPL. It is completely fine to statically link it.

EDIT: But there are some extra things you have to do: https://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic

Fortunately we do have a steady influx of new people incl. those who demand shit to god damn work, finally shifting this notion.

What the hell is going on in this thread? Linux has been being actively developed by people who want “shit to god damn work” forever. What are the concrete examples of things that don’t work? Old games? Is that the problem here? These things that were developed for the locked in Windows ecosystem since time immemorial and never ran on Linux and now, through all of the work of the Linux ecosystem, do, by some miracle, run on Linux. It’s amazing that these things work at all: they were never intended to!

The Linux ABI stability is tiered, with the syscall interface promising to never change which should be enough for any application that depends on libc. Applications that depend on unstable ABIs are either poorly written (ecosystem problem, not fixable by the kernel team, they’re very explicit about what isn’t stable) or are inherently unstable and assume some expertise from the user. I’d say the vast majority of programs are just gonna use the kernel through libc and thus should work almost indefinitely.

But you can do that: Linux provides a ton of ways to use different versions of the same lib. The distro is there to provide a solid foundation, not be the base for every single thing you want to run. The idea is you get a core usable operating system and then do whatever you want on top of that.

Just fyi containers use pivot_root not chroot

Thought it was 0 0/2 * * * at first lol

I don’t care to join in on the rest of this discussion but:

Hold you accountable for what? Nothing being done here is remotely illegal.

The definition of “illegal” could change in a future government. This is one of the strongest arguments for internet privacy in general: what is legal today may be “illegal” tomorrow or even “legal but the government doesn’t care about the law”

I watched Jurassic Park with a live orchestra playing all the music and it was rad