linuxmemes

29804 readers

1539 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

Instance-wide TOS: https://legal.lemmy.world/tos/
Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html

2. Be civil

Understand the difference between a joke and an insult.

Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".

Don't get baited into back-and-forth insults. We are not animals.

Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.

Bigotry will not be tolerated.

3. Post Linux-related content

Including Unix and BSD.

Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.

No porn, no politics, no trolling or ragebaiting.

Don't come looking for advice, this is not the right community.

4. No recent reposts

Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.

5. 🇬🇧 Language/язык/Sprache

This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸

Comments written in other languages are allowed.

The substance of a post should be comprehensible for people who only speak English.

Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.

6. (NEW!) Regarding public figures

We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.

Keep discussions polite and free of disparagement.

We are never in possession of all of the facts. Defamatory comments will not be tolerated.

Discussions that get too heated will be locked and offending comments removed.

Please report posts and comments that break these rules!

Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

founded 2 years ago

MODERATORS

poopsmith@lemmy.world

zephyr@lemmy.world

rtxn@lemmy.world

1097

No comment (sh.itjust.works)

submitted 5 days ago by Lisk91@sh.itjust.works to c/linuxmemes@lemmy.world

165 comments fedilink hide all child comments

🪿

you are viewing a single comment's thread
view the rest of the comments

[–] qqq@lemmy.world 1 points 2 days ago* (last edited 2 days ago)

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.