@piggo@piggo.space@lina@vt.social@foxido@social.cutie.team Which I think is fundamentally different from the systemd problem. I think systemd covers all usecases pretty well and most people who purposefully avoid systemd do it moreso for ideological reasons (i.e. the unix way, etc.).
For Wayland I can actually say there's a lot of software and hardware setups that do not work properly, while they do work on xorg.
@piggo@piggo.space@lina@vt.social@foxido@social.cutie.team Yes, I agree. A lot can be said about the fact that even after 17 years Wayland still does not cover every user's usecase and some people still prefer to use xorg because of it.
@SuperDicq@piggo@lina@foxido I was aggressively against SystemD because it was forcibly shoved down our throats way before it was ready. I won't accept arguments on this because I was, every year for years, hampered by critical problems that weren't being backported to LTS distribution releases. But today it works fine and I use it happily.
I am still not ready to switch to Wayland. But admittedly I am not using high dpi monitors or mixed resolution multi monitor where Wayland is supposed to have advantage.
Like SystemD I'll switch when I'm absolutely forced, but I will not stop complaining until it stops causing me problems.
@sun@SuperDicq@foxido@lina it was a no go for me before jetbrains ported the entire fucking java gui toolkit, themselves, to make the ides work on Wayland
There is no "market" and it doesn't matter what people use. You should try to write software that covers everyone's usecase as best as you can and then ultimately let people decide what they want to use.
@sun@SuperDicq@piggo@foxido@lina It seems like a good comparison in that everyone wants to be a late adopter, but certain entities (uncooperative dependencies) being late adopters is actively harmful to the process and it becomes a chicken and egg problem for adoption.
@SuperDicq@piggo@birdulon@lina@sun@foxido Gnome and by extension also Wayland is mostly developed by people like this. Writing software for most usecases isn't their goal. They are writing software for their usecases. You can still see that in the GitLab issue discussing extensions to Wayland made by a Valve employee on GitHub and Wayland developers frustration by not using their normal channels when it was stated that the reason why they did so in private is specifically because the normal channels are too slow and mostly achieve nothing.
@phnt@SuperDicq@piggo@sun@foxido@lina Fair, I spend more time on macOS and Android devices these days. Sway was the first wayland compositor that I considered worth using, and various things pushed me to Hyprland, but everything is tolerable to me at best.
@phnt@SuperDicq@piggo@sun@birdulon@foxido@lina the devs in the projects cause the most friction, actively hampering the usability for users its so unfortunate that most "open source devs" in current year only care to write software for their end goals and not because it can benefit everyone. This is really prominent when you follow any drama from these people. Users never mattered
@birdulon@phnt@SuperDicq@piggo@sun@foxido@lina i mean sure, you can say that, but regardless it still impedes the general use case. Id argue that software thats designed for a single goal/usecase should not be used by other people outright.
@theorytoe@phnt@SuperDicq@piggo@sun@foxido@lina >only care to write software for their end goals and not because it can benefit everyone It's fine on an application level, and the alternative is people just not sharing what they make for themselves. It's abhorrent on a toolkit level and people absolutely need to be shunned over it.
@Suiseiseki@freesoftwareextremist.com Maybe a fun project idea would be packaging GNU Shepard for Gentoo, as it I believe it is currently only packaged on GNU Guix.
@SuperDicq If I was going to do that, I'd may as well write my own 100% free GNU/Linux-libre distro without proprietary degeneracy like "nonguix" or CoC's.
@Suiseiseki@freesoftwareextremist.com I'm fairly certain that starting your own distro is exponentially an insane amount of more work than just packaging an init system.
I personally have no problems with "degeneracy" in GNU Guix. While I am not a fan of CoCs I do not think the CoC, how it is implemented on GNU Guix is actively int the way of software development.
Nonguix is also not officially part of the project, as it should be, and on top of that comes with the appropriate warnings that every user should read before they decide to install proprietary software.
@Suiseiseki@freesoftwareextremist.com Gentoo is much worse when it comes to enforcing software freedom than GNU Guix so I don't understand why you would rather use that.
@SuperDicq >starting your own distro is exponentially an insane amount of more work than just packaging an init system. Having to write init files for every single package for Gentoo is a similar amount of work than writing a package manager really.
@SuperDicq Gentoo has USE flags - I can actually compile the software to not come with JavaScript support by setting USE value without having to work out inanely named package flags.
@sun@phnt@SuperDicq@piggo@birdulon@foxido@lina shoot your shot if ya wanna, I'm not gonna change my mind on gnome, since everything else I've used feels substandard in comparison, even windows. I have it slightly customized with some extensions that don't even change the core workflow
@Suiseiseki@freesoftwareextremist.com If you make your own distro you have to write your own init files for every single package too, on top of all the other work that comes with making your own distro
> decency probably right on the money? I'm not sure. I've told many people to get fucked over how gnome changes things that affect them but not me (and that benefit me since they make gnome better) so bleh
@SuperDicq@piggo@birdulon@lina@a1ba@phnt@sun@foxido related to this, i maaaaaaaaaybe if i dont get a macbook will get a gaming laptop, which obviously will have an nvidia gpu, supposedly nvidia+wayland just works
@SuperDicq@piggo@birdulon@lina@a1ba@phnt@sun@foxido@mischievoustomato Clearly the latest nvidia cards are not going to work, but Nouveau does support almost all Nvidia cards - in the cases where a non-handcuffed card does not work, usually a bug report to Nouveau developers with enough details would allow them to support it.
Wayland on this machine randomly crashes about once a day (I did notice it becomes more common after the laptop was recently suspended) becoming completely unresponsive and requiring a hard reboot. This does not happen on Xorg on the same machine. I run Debian stable with KDE.
@phnt@SuperDicq@piggo@sun@birdulon@foxido@mischievoustomato@lina gnome 3 happened because the gnome project heard that microsoft was going to implement the same ui across PCs, phones and tablets, and copied the idea before microsoft even committed to it. i gave it an honest try several times over the years, and each time the experience was worse
@a1ba@phnt@SuperDicq@piggo@sun@birdulon@foxido@lina idk. When I had a ryzen laptop I had to use Windows if I wanted to have a stable experience and not have crashes every other time because I dared watch video or game. Hell, when I dropped linux on it, it was so bad the amdgpu driver would crash just randomly. And I still see issues like those now and over the years. Just the other day I read a guy that switched to an intel mobo on the framework laptop due to amd being unreliable.
@a1ba@phnt@SuperDicq@piggo@sun@birdulon@foxido@lina as per my visits to places like the arch forums, kernel bugzilla and the that thread on hacker news, 1 month or about a week ago are the latest things like that
And on top of that Xorg at least has a good excuse for not covering as much usecases as possible. Xorg was purposefully abandoned by its developers who blocked anyone who tried to implement any new features into upstream, hence why forks exists now.
Almost quote: A lot can be said about the fact that even after 41 years X11 still does not cover every user's usecase and some people prefer to use Wayland because of it.
@SuperDicq@piggo@lina@foxido Wayland is a protocol too. While Xorg is not as old as X11 it still 1) older than any Wayland compositor, 2) not written from scratch but is a fork of XFree86, so code base still 34 years old. While, for example KWin Wayland is about 10 yo.
@taylan@fedi.feministwiki.org@Suiseiseki@freesoftwareextremist.com The CoC was a declaration of hostility towards feminism, so I asked to make it neutral instead, and that was the problem.Your definition of "feminism" is active discrimination and the opposite of human rights.
@SuperDicq@Suiseiseki No, I never had any problems with anyone. The CoC was a declaration of hostility towards feminism, so I asked to make it neutral instead, and that was the problem.
Why should I contribute to a project that says "fuck you, we don't want you here because you care too much about human rights"?
Nope, the CoC literally intentionally leaves out mention of sex-based discrimination while listing every other under the sun, because the author is a male person hostile to feminism.
If you consider caring about the human rights of persons of the female sex to be discriminatory, then you're no different from a run of the mill sexist dude screeching about how feminazis want to forcibly castrate men. It's deluded.
@SuperDicq@Suiseiseki You can keep telling that to yourself so you don't have to confront the fact that CoCs are an utter and complete catastrophe that make many projects actively more anti-feminist. I hope one day you'll wake up and choose to confront reality instead.
@SuperDicq@Suiseiseki Yeah, I could see that. It seems that some men who don't care about sexism often become actively more sexist when people complain too much about sexism, because "not being annoyed" is more important to them than human rights. Maybe it's good to make people show their true face though, so I'm not sure I should be concerned by that or try to appease them.
> I was aggressively against SystemD because it was forcibly shoved down our throats way before it was ready.
Absolutely.
I think it's also completely un-auditably large. Any other init system is a few thousand lines with no dependencies; Lennart's is 28k with DNS client/server, HTTP client/server, XML and JSON parsers, basically everything that has ever created a vulnerability in code. Entire classes of vulnerability that did not exist do now. The xz rootkit that opened a hole in sshd could only do so because sshd had to link against systemd, which linked against xz: that rootkit would have been impossible without systemd. (Ask me how I feel about PAM.)
@SuperDicq@piggo@lina@sun@foxido That's naive, ecosystem shifts necessarily require cooperation, and many players simply won't cooperate until "forced" to. Godot rejected a Wayland support PR years ago claiming that they didn't see a point in adding more code to maintain when Wayland users could just use Xwayland. Apple played hardball on legacy APIs, so Godot 3.x has HiDPI support on macOS and will likely never have it on Linux outside of custom builds. Godot is far from the only project that refused to play ball, even when handed the requisite code on a silver platter, and all of them had the "well other projects don't support it so why should we" attitude. And that's just in open source land — proprietary Nvidia drivers are far harder to secure cooperation from, and that's a huge blocker for many users.
@SuperDicq@Suiseiseki init files aren't hard to write; how many daemons do you plan to run? `wc -l /etc/rc.d/*` shows about 2000 lines on my machine and I have a lot of stuff installed. Most of those lines are duplicates: "case $1 in", etc.
@p@fsebugoutzone.org@Suiseiseki@freesoftwareextremist.com You probably misunderstood the topic. If you are maintaining your own distribution you have to maintain init scripts for every single package, not just the ones that you have installed, in order to distribute it to other users who might install that software.
@SuperDicq@Suiseiseki Me after I rip off my skin and muscles because that's how much I hate sexism.
No mate, the sexism is in the Contributor Covenant (#CoC used by #Guix). The author literally doesn't want to acknowledge sex-based discrimination, because he's a man who wants to be a woman, and cannot deal with the fact that humans have a sex and males are not female. That's really all there is to it. Trans to anti-feminist pipeline.
And because men dominate IT, he successfully made software projects everywhere (even Linux) adopt his bullshit CoC that validates his weird anti-feminist world-view in which people are never discriminated against on the basis of their sex.
Men literally said "we're women too now because we like feminine gender performance, and there's no such thing as sex, and no such thing as sex-based discrimination" and the software industry said "OK" because that's how little it cares about women. More important to appease the weird anti-feminist guys than to stand up against sex-based discrimination.
You could actually argue that it makes sense in a twisted utilitarian sense, because there's a lot more of those weird femininity-obsessed, anti-feminist guys in IT, than there's women passionate about battling sex-based discrimination. So if you have to make one of these two groups angry, it's strategically "smarter" to screw over the women and appease the sexist trans guys.
But I'm not gonna be a part of that. And I'm not gonna let them get away with it without at least having this one schizoid lunatic on the Fediverse (me) constantly and endlessly bitch about their sexism.
Because Guix was literally my favorite free software project ever, and they aggressively took that away from me. The least I can do is get on their nerves and make absolutely sure that they have to face what they did.
> If you are maintaining your own distribution you have to maintain init scripts for every single package,
Only the ones that require init scripts, which is a tiny fraction of the packages. The vast majority are libraries. Build scripts and version numbers are a bigger headache. init scripts are nothing.
> not just the ones that you have installed, in order to distribute it to other users who might install that software.
If more people than you are using your distro, then maybe; aside from that it doesn't have to fit any use cases but your own. Someone else comes along and asks for something, sure. But you don't have to eat the entire mountain the second you sit at the table. There are a million packages in Debian because Debian is huge and relatively monolithic. SteamOS doesn't have to have PostgreSQL or zgrab or R; CoreOS doesn't have to have a GUI; EmulationStation doesn't have to have etc. If you are rolling your own distribution, it doesn't have to have anything.
@p@SuperDicq@piggo@sun@foxido@lina >sshd had to link against systemd No it in fact did not - Debian made a patched version to add notification support, which of course indirectly made it link against libsystemd.
libsystemd indirectly linked against xz-utils, which allowed a sneaky backdoor where proprietary software added to xz-utils could hijack sshd.
The proprietary malware developers were clearly quite skilled and probably could have pulled off a better backdoor that didn't only impact some systemd systems if there wasn't such a sneaky option - but now they've had to start from square 0, as they've gotten caught.
> So, yes, usability is important and Linus being able to bind his mouse > buttons to whatever he wants is important, I guess. But it's probably > not what's stopping Linux from dominating the desktop market. What's > holding Linux back on the desktop? Applications, device support. Time, > also. The printing dialog? I don't know.
It is still not the Year of the Linux Desktop and we are still letting these lunatics drive the ship.
@taylan >the software industry said "OK" because that's how little it cares about women The proprietary software industry doesn't care about women - all it cares about is dominating women with proprietary software just as hard as men.
@phnt@sun@SuperDicq@piggo@birdulon@foxido@mischievoustomato@lina GNOME may be “free software” to nerds like @Suiseiseki but when the developers are so utterly hostile to customization and 3rd party compatibility, and the users don’t get a say in the direction of the project, in practice it is absolutely no more “free” than the MacOS desktop, less so in fact because at least on Mac I have greater freedom of choice in what software I can run. https://macmenubar.com/ is a treat.
For the parts that are free software, you have infinitely more freedom that with the proprietary malware GUI in MacOS, as you do have the source code to make whatever customization you would like - people have made a library modification that re-enables theming for example.
>he needs proprietary software to add a menu of shortcuts ngmi.
It did have to hook into the logind stuff that SystemD does; I know of two distributions that didn't fall for SystemD (CRUX and Slackware) and one of them (Slackware) still added elogind, without which many login processes just fall over. If you mean it didn't have to link against their library, I am pretty certain that this is required unless you do it indirectly.
> libsystemd indirectly linked against xz-utils, which allowed a sneaky backdoor where proprietary software added to xz-utils could hijack sshd.
Yes.
> The proprietary malware developers were clearly quite skilled and probably could have pulled off a better backdoor that didn't only impact some systemd systems if there wasn't such a sneaky option - but now they've had to start from square 0, as they've gotten caught.
They were targeting a specific set of systems; the build script actually kept the vulnerability from being compiled into non-rpm packages. (Meaning the target was probably a government system with Oracle or IBM as the vendor.)
If you broaden the surface, you make it easier to get in. It doesn't really matter that he could have in theory done something harder: he had to put in a very long time with the xz project and that project was a weak link. The fewer links you have, the less the possibility of a weak link.
(I mean, to the point, I'm in agreement with most of the people in the thread: I do not like X11. It is massive and horrifying and it's a miracle that it works. But it does at least work; Wayland is a disaster. I don't think having the init system talk to the network has made the computer work any better or given it the ability to do something that it could not do before, and the cost is an exponentially expanded attack surface: at least X11 has a good reason to be able to talk to the network.)
Allowing you to be an asshole in the projects means that people will leave the project.
So removing you from the mailing means it is a net-win for the project. You lose 1 contributor who is an asshole and in exchange you get multiple new contributors in return.
So all you had to do was shut your mouth and not be an asshole. Is it clear to you now?
I'm sorry but I just completely stopped caring about that accusation. The word is equivalent to "heretic" to me now, because all you need to do for someone to use it is break a taboo by making a factual statement some people don't want to hear.
@mischievoustomato@SuperDicq@birdulon@foxido@lina@phnt@piggo@sun It only makes sense if you think of Linux as a consumer product that you want to push and you are still stupid enough to think that there will ever be a Year of the Linux Desktop. It won't happen because these people are dead-set on making Kirkland Signature Windows (and Windows is downstream of OSX anyway) and they are willing to burn all of the good shit just to achieve something that has zero value.
@taylan@SuperDicq@baleine The hate is the proprietary restrictions about what you must think and must not think and what you are permitted to write and that you are not allowed to write.
> It's hard to cover use cases you don't know about
But really easy to declare that there are no use cases you don't know about and that Wayland is the future. If they actually didn't know about these use-cases, that's a problem the Wayland devs created.
@a1ba@phnt@SuperDicq@piggo@sun@birdulon@foxido@mischievoustomato@lina we need egl and vulkan wsi over dmabuf implementation. Now almost every EGL driver implements device platform, which is enough to fully implement wayland and x11 platforms over it. But instead we are using internal x11/wayland platform implentations. Same for vulkan wsi. Even vulkan-wsi-layer requires internal VkSurfaceKHR implementation, that hides dmabuf or nvidia internals under it.
The year of the GNU/Linux desktop was around 1995 or so, as finally you could use a recent computer in freedom again - alas that freedom was savagely ripped away with the first of many proprietary programs added to Linux in 1996.
If a 1000% proprietary year ever results and what the prophesied "Year of the Linux [+ 9999 proprietary malware programs] Desktop" occurs, it's all over.
@p@phnt@SuperDicq@piggo@sun@birdulon@foxido@lina I'm a normal user and want it to work nicely. If I have to extend stuff, I use gnome extensions but in general it works as I need and even better often. There'll be environments for nerds as there always are, it just wont be on gnome or whatever.
Also the fact that you can’t imagine a GUI extension that’s any more complex than a couple of lousy shortcuts only proves my point about the Mac desktop being so far superior that it is actually pitiful how few real options you have in designing your workflow on Linux. Cool, you have a useless system monitor and can run pywal to get an unreadable low-contrast color theme going on in your polybar, let’s see it let you drag and drop a bunch of differently formatted photos onto it and have it intelligently optimize them for web publishing, or transform text in whatever app you’re currently using, or search the text of your last n visited web pages, or draw anywhere on the screen while presenting (not that Linux users ever present or even work a real job where they’d have to), or intelligently provide shortcuts to in-app functions, or provide literally any sort of productivity and task management tools more complicated than a stupid pomodoro timer. GNU/Freedumb is great if you’re stuck in the 1980’s.
> Well, yeah, this is why top-down ecosystems like Apple are able to have Apple Silicon moments
It's also why you can't grab a copy of OSX and run it on a dinky RISC-V SOM that you bought from some shifty manufacturer in Shenzhen for $10. Apple can dictate things because they maintain control over everything: I took this side of the trade-off, and it's foolish to try to sacrifice the advantages in order to make an attempt to get something that you could already have elsewhere.
> to the point that I recommend it to normies
I don't expect normies to want the computer to do the same thing that I want the computer to do.
> I'm *really* hoping the Linux desktop experience returns to where it relatively was in my estimation from like 2012-2019 because I do care about it and want to be able to recommend it again,
Before PulseAudio broke sound and the YOLD GUI toolkits drove the final nails into the coffin.
A chef is going to be faster with a knife than either of us is with a food processor; I'm not a professional chef, though, so I don't expect to use the same tools that a professional chef does. I don't want to go into his kitchen and fuck up his knives on the grounds that I'm making his knives better for a wider number of people, though: I'm fine with using normie kitchen implements. It's the same for any profession. It is the same for this profession.
> Developers and nerds can do whatever they want, I'm not responsible for their computing choices :)
Except that you have just written a justification for "forcing cooperation".
@p@SuperDicq@piggo@sun@foxido@lina Well, yeah, this is why top-down ecosystems like Apple are able to have Apple Silicon moments and I'm able to have a good experience as a user to the point that I recommend it to normies that I care about.
I'm *really* hoping the Linux desktop experience returns to where it relatively was in my estimation from like 2012-2019 because I do care about it and want to be able to recommend it again, but for all I know, it will never be appropriate to recommend a desktop experience to these people again — just things like SteamOS and Android devices. Developers and nerds can do whatever they want, I'm not responsible for their computing choices :)
@BionicNigga@phnt@SuperDicq@piggo@sun@birdulon@foxido@mischievoustomato@lina >Not if you can’t code If are not willing to learn to program, you should not use a programming machine like a computer - it's like wanting to use a calculator, but being unwilling to learn how to use that complicated multiplication operation - you'll find yourself calculating something as simple as 5*5 by entering 5+5+5+5+5 and find that many calculates are infeasible to perform.
>if you don’t feel like spending the rest of your life patching obnoxious compatibility regressions You have the freedom to simply just not update the software and therefore no further patches are required.
>in designing your workflow on Linux My workflow is the GNUflow with the Church of Emacs.
>let’s see it let you drag and drop a bunch of differently formatted photos onto it and have it intelligently optimize them for web publishing Imagine being unable to use imagemagick or GIMP and needing some proprietary malware to hold your hand.
>or transform text in whatever app you’re currently using Yes, Emacs can do operations on text, although bloat.
>or search the text of your last n visited web pages Yes, that can be done in Emacs Web Wowser, although bloat.
>or draw anywhere on the screen while presenting Totally useless feature that is a benefit not to include - but yes there are free software programs that allows drawing on a Xorg session.
You can also present just fine in GIMP with tab mode and draw anything you want with the drawing tools.
>intelligently provide shortcuts to in-app functions Yes, the Church of Emacs has keybindings available for most operations and it is possible to keybind all operations to whatever combination you want.
>task management tools more complicated than a stupid pomodoro timer. The GTimer free software time tracker offers functionality that most proprietary time trackers lack.
>recommendation to run proprietary software. You are a itoddler.
Just for the record: When I started *that* thread on the Guix ML, I did so with a simple patch (to the CoC file) and a brief comment. I tried hard to avoid getting into off-topic arguments over ideologies (despite others trying to bait me into that), and tried to focus purely on the principle of "the CoC should not put any particular ideology over any other."
Certain others on the ML still saw that as an ideological attack, because of a certain aspect of how their ideology works: "Anyone who doesn't submit to these rules is an enemy."
@SuperDicq@baleine@taylan >if you're working on a project anything posted on official channels should be about the project and not distract anyone from just getting the shit done. But that is not what any CoC contains and requires.
There is no problem with a guideline advising that anything posted on official channels should be about or related to the project and that other posts should be made on other channels, as that is not a proprietary restriction.
CoC's are about demanding obedience in what people think and punishing any deviance, even if such punishment goes against getting things done - for example the removal of developers who make good contributions, but commit wrongthink and wrongwrite (which you can just ignore - don't read it if it's not a patch - there is free software that can do automatic filtering for you).
@taylan Really not to be pedantic, but isn't sex a sex characteristic itself? In my reading "sex characteristic" is somewhat more abrangent than just "sex".
> I'm a normal user and want it to work nicely. If I have to extend stuff, I use gnome extensions but in general it works as I need and even better often.
Last I heard you were running Windows and you liked it better; if you're running Gnome, it's news to me. I don't actually care if people run Windows.
> There'll be environments for nerds as there always are, it just wont be on gnome or whatever.
I have never in my life run Gnome. I've had to use it a few times; I do not like it. I would have zero complaints if "not running Gnome" actually insulated me from this shit. Same reason I don't actually care if people use Windows until Microsoft starts doing shit that encroaches. The Wayland project has the idea that they have to actually eradicate X in order to succeed.
This is a problem that *all* of these projects have. System Dee, Rust, Wayland, PulseAudio, and the reason for this is, if you skip the mailing list and read the slideshows they present to their investors, an attempt to control the ecosystem: it's not an attempt to make the software better, it's an attempt to eliminate alternatives that aren't controlled by a single vendor. Lennart even let this slip on a public mailing list a couple of times when discussing SysDem"D". It is the standard Red Hat template; it is not a coincidence that Wayland started at Red Hat.
@p@phnt@SuperDicq@piggo@sun@birdulon@foxido@lina i ran windows be ause i couldnt run linux because amd's drivers were superass. I have ran gnome since 2020, 2021 onwards with the new intel laptops i got
@BionicNigga@phnt@SuperDicq@piggo@sun@birdulon@foxido@mischievoustomato@lina The June 2025 TOP500 list has been published: https://www.top500.org/lists/top500/2025/06/ . Zero of those machines run Windows. I am more interested in that shit than forcing YOLD to continue to never happen. (I'd rather push "year of the home supercompute cluster" than "year of the Linux desktop". My mom is now running Slackware on her all-in-one system that sits next to her work desktop: it doesn't matter because any OS will show her Youtube videos.)
@SuperDicq@piggo@lina@mykolak@foxido Well at least my favorite piece, "BEWARE: the docs lie!" in randr.xml has been unchanged for 19 years and so was probably inherited from XFree86.
The vast majority of people can indeed learn to program - they are just told that they can't and they should leave it up to the proprietary master.
A few decades ago it was discovered that secretaries learned to program in the Church of Emacs, when provided a manual how to use the editor, which they did not hesitate to follow, as it didn't say that want they were doing was programming.
>The myriad excellent software options available on a Mac The jokes write themselves.
For software to be excellent, a prerequisite is not being proprietary malware.
You can quite easily have a functionally good program that is a disaster, as it takes the users freedom - which is clearly not excellent.
>it’s a pity you can’t use them because your rigidly restrictive proprietary mindset says so It's not a pity that I haven't surrendered my freedom to apple.
That's like writing that declining to put your arms and feet into shackles and gleefully taking any abuse is a "rigidly restrictive proprietary mindset".
>is maliciously stupid advice in the era of 24/7 networking It's something called not exposing the program to the internet via a firewall you keep updated.
>will inevitably cause compatibility problems as soon as you want to run a newer program. The absolute state of the macos-addled brain.
As there are no proprietary restrictions, it doesn't matter what version of unrelated programs you have installed - you can have the most bleeding edge packages installed next to 20 year old software on the GNU system with no issues.
Even if you do have some old program with a cursed old dependencies, you do something called moving all the needed .so files into the same directory, or throwing the old program in a chroot with the old library versions and it will continue to work forever.
>computing experience on Linux, the operating system. A false claim doesn't become true just because you repeat it over and over - that is a toddler level of thinking.
>macOS predates iOS you dingus. All apple users have mentally been (i)toddlers ever since apple targeted the "market" of the hopeless.
@Suiseiseki@phnt@SuperDicq@piggo@sun@birdulon@foxido@mischievoustomato@lina The vast majority of people cannot code, and they shouldn’t have to. The myriad excellent software options available on a Mac prove that computers can be incredibly useful to non-coders, it’s a pity you can’t use them because your rigidly restrictive proprietary mindset says so. And “just don’t update it then” is maliciously stupid advice in the era of 24/7 networking, and will inevitably cause compatibility problems as soon as you want to run a newer program.
> everything people actually want from a computer is bloat
Typical freetard cope, though I’ll grant that emacs is probably the closest thing you’re going to get to a cohesive computing experience on Linux, the operating system.
@BionicNigga@phnt@p@SuperDicq@piggo@sun@birdulon@foxido@lina Linux's biggest issue is how fragmented it is and how many things developed seem to be like mediocre alternatives to windows or mac's systems. Genuinely, when I get a good job, I could just get a macbook and game using either native stuff or crossover and be happy
@p@mischievoustomato@phnt@SuperDicq@piggo@sun@birdulon@foxido@lina YOLD garbage killed any interest I had in Linux as a desktop system and drove me to Mac since that’s what it’s become a shitty imitation of. If I ever come back to it, it will only be for hobby computing on an old laptop with a 20yo version of Slackware or something. That or maybe BSD which I hear isn’t as pozzed though idk that might just be a meme.
> I'm advocating for upstream dependencies to support wider protocols and configurations.
Combinatorial complexity. I have to use this shitty browser and this shitty browser links against gtk3 because of course it does, and gtk3 has somehow become so intolerable that the GIMP team, which created gtk, refused to use it. The Wayland psychopaths actually *do* want to kill X.
> I care about this which is why I would bitch about projects needlessly refusing to accept PRs for building for RISC-V.
My point was Apple doesn't take your PRs. There is the flexible approach that lets you drive, and then there is the top-down system which cannot tolerate you driving. You look at the "Worse Is Better" part of Dick Gabriel's famous talk (in case anyone that hasn't read it happens upon the thread: https://dreamsongs.com/WIB.html ), and it was the same kind of fretting over Unix doing the wrong thing and being kind of a clunky pain, you read what almost any of the Lisp guys were saying in the 80s, or you look at the "Unix Hater's Handbook" and read all the rants. Unix went everywhere by being simple and flexible: maybe Apple's integrated supply chain can achieve things in the short-term that an open system of interchangeable parts cannot, but the advantage is just a marketing advantage that never lasts too long, and in the mean time, hackable code always seeps into places that a marketing division can't even see, let alone target.
And like I mentioned in the other post, TOP500 and OpenMPI and Plan 9 and whatever else: these represent large qualitative shifts. "Wayland? Well, let me tell you: the compositor is built in! NO TEARING!" It's not impressive, it's sure as hell not worth disrupting things that already work. Hitting a performance target that won't be impressive next year, minor UI changes, these are not even going to be footnotes. It's marketing caring about their Q3 push because the big boss wants to have some impressive graphs during his quaterly meeting with the board.
(Anyway, as far as PRs for building for RISC-V, so far it's been a surreal experience: everything works. I have spent so many years with ARM systems and a lot of 64-bit ARM stuff *still* takes some fiddling to build but nothing has ever given me trouble on RISC-V. I'm too shocked to be impressed.)
@p@SuperDicq@piggo@sun@foxido@lina >Except that you have just written a justification for "forcing cooperation". I'm not advocating for restricting the computing choices of users, I'm advocating for upstream dependencies to support wider protocols and configurations. >It's also why you can't grab a copy of OSX and run it on a dinky RISC-V SOM that you bought from some shifty manufacturer in Shenzhen for $10. I care about this which is why I would bitch about projects needlessly refusing to accept PRs for building for RISC-V.
> YOLD garbage killed any interest I had in Linux as a desktop system and drove me to Mac since that’s what it’s become a shitty imitation of.
It's a shitty imitation of Windows, which is a shitty imitation of OSX.
I don't have much interest in the typical "desktop computing" stuff, so except that the "desktop" people keep fucking up things that used to work (for about 10-15 years, sound *always* worked on Linux; then PulseAudio came), it doesn't bother me. But what birdulon was saying, you know, the actual YOLD is Android. That's fine with me; Android doesn't fuck up anything I'm doing. The horrible Gnome devs do.
> That or maybe BSD which I hear isn’t as pozzed though idk that might just be a meme.
OpenBSD is still run by the coders instead of the feelings.
I basically run Linux just because it is the best thing that works on my hardware. I'd rather be using Plan 9 most of the time, and most of my screen space is dedicated to drawterm sessions talking to Plan 9 machines. There's Linux stuff I have to have for work reasons, you know, there's no commercial interest in Plan 9, which is why no "Year of the" dipshits have arrived to ruin Plan 9 yet, but it's also why a lot of stuff won't get a port unless you do it yourself.
@Suiseiseki@phnt@SuperDicq@piggo@sun@birdulon@foxido@mischievoustomato@lina > anyone can code! Blank slate bullshit, those secretaries were probably >85th percentile IQ at least, and that’s not remotely the same thing as having to maintain a user-hostile OS because “muh freedumb” when you could just use Mac.
> Church of eMacs Definitely not a cult.
> using good software is slavery The GNU/delusion is strong with this one. Freedom as you define it does not exist.
I mean Gnome! I love touchscreens... and feet? Keyring wasn't unlocked at boot? Look, I'm not very good with computers, how did this get here? Jaypeg.mp4
@SuperDicq@piggo@lina@mykolak@foxido It's code in the same way that C header files are code, it's just in XML because it's binary-format IPC description and allows to generate code in any language rather than being stuck to one like C (which has a lot of drawbacks).
And XML is used for a ton of stuff that aren't configs, like if efficiency didn't matter, it could just be XML as the payload (hello XMPP, OStatus, AJAX, …).
This looks like an issue to someone that wants the end result but doesn't care about the rest of the process; the rest of the process is required to achieve the end result, though.
> how many things developed seem to be like mediocre alternatives to windows or mac's systems.
This isn't a Linux thing, this is a Linux DE thing. Look at the TOP500 list: why are they not running Windows or OSX? It's because those operating systems are missing things that Linux does have: it's just not parts of the OS that you use, so it's not stuff that's visible to you. El Capitan churns out 1.742 exaflops: nobody asks why it doesn't play games. Why don't they use Windows? Is it because everyone that owns a supercomputer cares about your freedom? Of course they don't. Microsoft has the #5 system on that list: what are they running on it? https://www.top500.org/system/180236/
> Operating System: Ubuntu 22.04
Windows is unsuited to such an environment.
There are very small systems, too. Windows doesn't run on those, either. OSX doesn't run on those. Desktop systems are a tiny sliver: they're just the consumer-facing sliver. Desktop shit doesn't matter anywhere else computing happens. The desktop is the least interesting part of the entire massive world.
I saw your post about this and I was completely unable to figure out the...any of the idea. Then you posted an hour(?) later and said it was good and I wasn't sure what to do with this information. Like, in theory I can understand some facet of it if I try to consider putting peanut butter onto a banana.
And here I was thinking that having a robust software ecosystem and a variety of choices for different needs and tastes was a good thing, but ok.
I’ve always hated this line, not least because if the YOLD nuts ever had their way you just know the one DE and distro they’d standardize on would be GNOME and Fedora. Or Ubuntu, pick your poison.
Oh wait you were being autistic and talking about the kernel, because your entire personality revolves around relitigating a naming controversy from like 30 years ago that no one cares about. Get a hobby.
@p@fsebugoutzone.org@BionicNigga@poa.st@mischievoustomato@tsundere.love@phnt@fluffytail.org@SuperDicq@minidisc.tokyo@piggo@piggo.space@sun@shitposter.world@birdulon@shpposter.club@foxido@social.cutie.team@lina@vt.social The horrible Gnome devs do.Most whatever-open-source devs are horrible since the whole industry is now filled with troontards, commiefaggots and pajeets.OpenBSD is still run by the coders instead of the feelings.It's the only reason I've considered jumping to whatever-BSD, and will probably do in the future after the whole Xlibre clusterfuckery.there's no commercial interest in Plan 9, which is why no "Year of the" dipshits have arrived to ruin Plan 9 yet, but it's also why a lot of stuff won't get a port unless you do it yourself.F... I wish there was a more "friendly" Plan9 version/distro/thing and not something I'll tinker with in 15 years when I'm retired and living as an expat in Thailand and working a small plot of land or something :akko_weary:
> Most whatever-open-source devs are horrible since the whole industry
The projects that intersect with commercial interests tend to reflect corporate values.
> It's the only reason I've considered jumping to whatever-BSD, and will probably do in the future after the whole Xlibre clusterfuckery.
Yeah, every year I evaluate whether I can really stand to keep using Linux.
> F... I wish there was a more "friendly" Plan9 version/distro/thing
Well, there's 9front, and it's easy enough to install but it's not friendly. On the other hand, a cockpit is somewhat unfriendly to someone used to driving a car, but pilots still have all of those dials and buttons and gauges instead of just a single button that says "GO". It's unfriendly because it's designed to be useful rather than friendly.
>Combinatorial complexity. On builds yes, on codebases not really. Media players supporting ALSA+OSS+Pulse+Jack backends didn't have to care about how that interacted with the other configs for the most part. Even then, plugins can tame the number of builds to package.
>TOP500 and OpenMPI and Plan 9 and whatever else: these represent large qualitative shifts. "Wayland? Well, let me tell you: the compositor is built in! NO TEARING!" It's not impressive, it's sure as hell not worth disrupting things that already work. Correct, it's not impressive, it's the bare minimum. Treating a multimonitor setup as one big framebuffer synchronized to one monitor is below the bare minimum. I won't claim to never be interested in computers I don't have, but I definitely care more about the ones in front of me than supercomputers I will never interact with.
@phnt@p@SuperDicq@piggo@sun@birdulon@foxido@mischievoustomato@lina Oh wow, that is unbelievably bad. Freedom of choice is the only real freedom end users really have, and the thing that brings people to Linux, but then I’m just repeating something that’s been obvious for decades now when I say that YOLD types are completely out of touch with and do not care about the people who actually like Linux as a desktop for what it uniquely has to offer, and are a completely separate camp with entirely unrelated and even disparate interests.
@BionicNigga@phnt@p@SuperDicq@piggo@sun@birdulon@foxido@lina > and the thing that brings people to Linux the thing that brought me to linux is that it's different to windows and runs better. And well, I have the choice of running what I want. I'm not gonna force shit I don't care about running to be how I want it to be.
@BionicNigga@phnt@Suiseiseki@SuperDicq@piggo@sun@birdulon@foxido@lina but it doesnt have to be a thing for EVERYTHING. Gnome doesn't have to be as customizable as kde or other stuff is. It's autistically "itself" and that's why I love it. If you don't like it, just move somewhere else.
@birdulon@p@SuperDicq@piggo@sun@foxido@lina >Treating a multimonitor setup as one big framebuffer synchronized to one monitor is below the bare minimum. Xorg doesn't do that anymore since more than a decade ago.
You can still have that mode with certain software, which is kind of good for flightgear really, as you get fullscreen across 3 screens without needing configuration.
> RISC-V has benefited from years of popular ARM usage fixing up needlessly unportable code.
This would be my reasoning but if that were the case, ARM would not still be broken so frequently.
> On builds yes, on codebases not really.
This depends really heavily, and a complicated build is harder to test than a complicated program.
> Treating a multimonitor setup as one big framebuffer synchronized to one monitor is below the bare minimum.
It's a way of modeling the screen. It's fine with me. I'm using it right now.
> I won't claim to never be interested in computers I don't have, but I definitely care more about the ones in front of me than supercomputers I will never interact with.
Most people don't give a shit about Linux; I'd rather it be the year of the supercomputing environment on the desktop than the year of some OS that used to be a good workstation OS but was ruined by attempts to make it a desktop OS on the desktop. See attached. (How many cores do you have and if you told that to someone in the 90s, what would they think?)
But that aside, you've missed the point: that kind of environment is different, there is a massive breadth. You do not need to shoe-horn a solution that other operating systems have into an operating system that is designed to do something completely different. needcomputer.jpg
@Suiseiseki@p@SuperDicq@piggo@sun@foxido@lina Which part specifically are you talking about, because skimming the start is just talking about the views into the big framebuffer and I'm sleepy
>the choice of running what I want. You wouldn't have that if the retards like :ebussy: and his circle controlled Linux. Thankfully they don't and never will.
I knew it was destined to fail the second I read the description of it. They said that they were going for the low end of the market and the "developing world" because they didn't want to compete with Apple. You don't capture that market unless you can flood it, and Mozilla never had the budget for that. You have to make something unique that people want otherwise, and you have to cram a bunch of weird shit into the dev version so people will make weird shit: instead, they put these things on locked-down minspec shit phones and kept shouting "ACTUALLY HTML5 IS JUST AS CAPABLE FOR DOING COOL SHIT AS ANY OTHER PLATFORM, ACTUALLY YOU LOVE THIS" over and over. So it wasn't hackable, it was just a buggier version of Android, on a shitty phone, with a bunch of browser games that you could download.
@vokainen099@BionicNigga@RedTechEngineer@Suiseiseki@SuperDicq@birdulon@foxido@lina@mischievoustomato@phnt@piggo@sun They could have carved out a niche; instead they went for "cheaper than Android" which was a niche that doesn't exist. Like, the Pinephone has a niche that Mozilla could have filled: they have drifted really far since this, but they were the first company to do a big-ass IPO and then bank on open-sourcing their entire core product. Relentless browser enshittification aside, this pushed the concept, it was all people were talking about. "How are they going to make money if they're just letting people download the code? It doesn't make any sense!"
But yeah I don't think it would've ever taken off because unlike Android they do not have the capabilities to make 100 different OEMs install their OS by default like with Android so you're already way behind.
> assuming management could foresee google becoming dominant by forcing its browser unto Android phones
If you look at the Mozilla blog, you can see, like, after Chrome is announced, all people are talking about in the comments section is Chrome, and the Mozilla guys reply by tut-tutting. It should have been obvious that Google was going to eat Mozilla's lunch, especially to Mozilla.
I don't know if there's a price difference for different colors or what the deal is, but some manufacturers you really gotta pay attention to. wrong-race-of-slave-girl.png
@taylan Though I understand your point, I think misgendering someone that presents herself as a woman, and disrespecting her pronouns isn't very nice, not to say that is actually transphobic. I don't even know if that person is trans as you apparently try to state in a somewhat hurtful way, there are cis woman that don't ovulate or menstruate, and that doesn't them less woman, neither less cis.
In the specific matter of the Code of Conduct, I can see what you mean about the explicit usage of the term sex, and think it's a valid point, but it's difficult to have a conversation on that matter when arguments come together with disrespectful phrasing (phrasing that by itself already disrespects the code of conduct too).
I'm not a native english speaker, so I hope I made myself clear and managed properly to not sound rude, that's not my intent. Hope you can understand my point.
@anemofilia No, I don't think it makes sense to say that sex is a sex characteristic. A sex characteristic (or sex trait) would be a specific anatomic or physiological feature that relates to sex. They are divided into primary and secondary. Primary sex traits are those present at birth and directly involved in reproductive function, like the genitals. Secondary sex traits are those that develop later and aren't directly involved in reproduction, such as shoulder/hip width ratio and breasts.
Sex-based discrimination may relate to a specific sex characteristic in some instances. For example, a man could make a crude comment about a woman's breasts, or he could say that her hormones make her irrational, and so on.
However, the over-arching reason that sexism exists as an ideology is so that people of the female class can be exploited by people of the male class. And indeed there will be many cases in which the discrimination is not based on any particular sex trait of a woman, but rather the fact that she is classed as "female" in terms of sex categorization.
By the way, note that in the linked GitHub issue, the author of the CoC actually claims to be female. (He is male.) Under his ideology, people do not really have a sex, except as a legal category. They only have a disjoint set of sex traits, which can be modified, and their legal sex can be changed at a whim, and is just some text on a piece of paper or mutable value in a database. In this world-view, the discrimination against people of the female sex is erased from language, because there's not even any language to describe biologically female people as a distinct group from biologically male people.
@taylan I myself don't give much importance to pronouns, I couldn't care less if I'm called he, she or them. But there are people that care about it, and I don't think it's a big concession to refer to them by their preferred pronouns. I can't see how this is similar to the religious case, you already use pronouns to refer to people anyway, how does it really impact you to use the ones that people are okay with?
See, I have some disagreements with your views in that regard, but the primary purpose of communication is to communicate. If you can't express yourself in a way that people understand, and more than that, in a way people are willing to hear, you simply won't be able to communicate yourself. Of course you can "reserve the right to speak in any way [you] think is objectively right", but people can also reserve the right to not hear you if they think you're not being reasonable. Trying to sound respectful is something good by itself, but also very pragmatic when trying to communicate ideas.
Even though if you don't mean to sound hurtful, it does sound very hurtful, it communicates much more disrespect than it communicates any point you're trying to defend. You probably are aware that being a trans woman is a lot harder than being a cis man, no matter at which point of life a person transitions. The fact a specific trans person had some success prior to the transition isn't indicative of any "benefits" of being trans woman, rather is a indicative of the objective benefits of being perceived as a cis man in our society. To transition is actually a very brave act, you risk a lot of the things you got so far, an limit a lot the things you can get in the future.
I see pronouns and such the same way I see religious language.
When I'm in Turkey, I sometimes use phrases like, for example, "selamın aleyküm" / "aleyküm selam" (Islamic greeting) out of habit or politeness, even though I'm an atheist. But I would not tolerate someone trying to mandate the use of these phrases (which some imams try to do), and would stop using them if someone tried to force me.
Likewise, I used to be fine with preferred pronouns (I even have a blog post from 2016 where I specifically state that I'm fine with that), until it became mandatory and closely associated with an ideology that I disagree with and which is being aggressively pushed on me. Now I often use gender neutral pronouns, especially if a person who may otherwise be offended is around, since I don't actively want to offend anyone, but I reserve the right to speak any way I think is objectively correct.
The author of that CoC is well known as a transwoman. (Their name is Coraline Ada Ehmke.) Transwomen are male human beings. An adult male human is called a man. Literally, transwomen are a subset of men. A woman cannot be a transwoman, only a man can.
I'm not pointing that out to be hurtful. Firstly, it's simply a fact, and secondly, it's relevant in political discourse. Ehmke achieved a good position in the IT industry as a man, before starting to present as a woman, at around the age of 30. He has never gone through the experience of trying to enter the IT industry as a woman, studying computer science as a woman, or any such thing. He appeared in the German radio once while I was driving to work (he's from Germany) and, based on his voice, I can't imagine that anyone around him genuinely believes him to be female.
The fact that he claims to be a "woman in IT" and posits himself as an expert on minority inclusion in IT is very dishonest, because he's literally a white anglo-saxon male; one of the most dominant demographics in IT. The fact that he uses this fake "minority inclusion" expertise to push a CoC document which straight up tries to deny that female people exist as a separate class from male people is frankly outrageous.
I understand that the way I speak is considered "disrespectful" but this is simply the result of how dominant the "gender identity" ideology is. Someone being openly atheist in the deep south of the US, or a conservative part of Turkey, will be met with similar accusations of disrespect. Those in power get to decide what is considered "polite" and acceptable to say.
Sorry about the long post. Just trying to fully clarify my logic.
@wolf480pl@waldi@SuperDicq@piggo@foxido@lina on this very network freedesktop developers were bragging about trying to kill xorg as a living project, please don't be willfully obtuse. this is a "we raised your rent, you are free to live under a bridge" argument
Also, I don't get the whole "shoved it down" part. Nobody can force you to update. If you have a working system on a particular computer that runs eg. Xorg and ALSA, why would you care what's in the newer version?
FWIW there are still setups/use cases that other init systems handle(d) better than even the most recent systemd (I have one such setup) but yeah, the shoving it down everybody throat before it was anywhere near close to usable was a major factor in its rejection. Ditto for PulseAudio.