Wayland is not killing smaller distributions. Who even came up with that batshit crazy idea?
Killing is overly dramatic, but it’s putting a burden on certain projects if they want to convert to it and not all have the resources to tank it. I don’t see Window Maker porting their toolkit to Wayland, for instance.
But XWayland exists so I don’t see what’s the fuss.
My comment was about distributions specifically and those package Wayland since ages.
Someone on reddit.
Might as well be someone on lemmy since you reposted it here?
Doesn’t mean I agree with it. It’s still an interesting topic to discuss IMO, hence the repost.
I mean you do agree with it, clearly.
I actually stated in the title I don’t.
Well that’s confusing because the meme is complaint text with Hulk saying that he sees this as an absolute win and you titled the post “I don’t” which means you don’t see this as absolute win and therefore agree with complaint text in the image.
Yes, I don’t see this is as a win at all… what’s your point?
Flatpak is good for diversity. Users don’t need to worry about whether the obscure distro they want to use has the software they want in its repos. If a distro supports flatpak it will work with most popular software out of the box.
Plus, developers can create their own repositories that can then be used on any distro.
Developers are exceptionally bad at packaging software though.
Still better than developers providing .tar.gz files or hosting an apt repo.
Depends, at least with the APT repo there is a chance they used lintian to avoid the worst mistakes.
So having 1 packaging format that works across distros is good.
Having run PostmarketOS on an old Samsung Galaxy tablet and now Arch on PineTab 2, Flatpak often works better than the native package manager. Especially with Wayland, many packages just work including touchscreen.
I may be misunderstanding flatpack, though I do understand the draw of all dependencies in one package.
One of the big things that drew me to linux some years ago was “oh, you don’t have to reinstall every dependency 101 times in a packaged exe so the system stays much smaller?” As well as in-place updates without a restart. It resulted in things being much much less bloated, or maybe that was just placebo.
Linux seems to be going in the flatpack direction which seems to just be turning it into a windows-like system. That and nix-like systems where everything is containerized and restarting is the only thing that applies updates seems to be negating those two big benefits.
X11 is already dead, and it will not become more or less usable it will always stay the way it’s and wayland will get better. that’s the difference and flatpak is just an option it doesn’t try to replace what’s already availible. spreading distrust and misinformation about these softwares doesn’t help
X11 is already dead
How do you mean that? I’ve been using X11 for like 17 years. i3 uses X11, and I will most likely not use another WM if I can help it. It’s perfect for me. X11 is available in the core repositories of all the big distros.
Curious to know what you mean by “dead”.
by dead I mean abandonware, not devoloped for anymore
Just because they don’t do full releases doesn’t mean it isn’t developed anymore. They switched to updating modules individually, with three updates made this month. Doesn’t sound very abandoned to me.
It’s on life support but it is doomed.
That’s not what the person I was replying to said, they said it’s abandonware and not being developed anymore. Which is not true.
It is not getting new features anymore. Just because the distro is packaging it doesn’t mean it’s not dead.
I heard Sway is very similar to i3. But I’m partial to hyprland myself
I’ll say that while it still has features that Wayland doesn’t it’s not dead, it doesn’t get updates yes but it still used by a lot of people for the fact that Wayland just doesn’t support some stuff that x11 does. Great example I have is TeamViewer and Nvidia+KDE
You made exactly the point I was trying to make.
I guess “dead” is a matter of definition in this case. 🙂
While TeamViewer is definitely neglected I use it often on Wayland and it works well actually!
In the past year or so it doesn’t shut down correctly. But the core functionality works well.
I’ve been experimenting with Rustdesk as an alternative because I doubt they’ll update the Linux client anytime soon. The Windows version looks like an entirely different application at this point
In terms of feature parity. I believe the only thing left is global hotkeys, which hyprland proved it can be done.
I love me some hyprland, it’s minimal enough to run on my 4gb ram foldable laptop with the same animations I have on my main laptop & desktop.
Wayland x Nvidia aside (on my laptop) it’s the perfect minimal environment for me.
Sway is essentially i3 + Wayland, so it shouldn’t be a hard switch once X11 goes EOL.
I actually used Sway for a while. Can’t remember why I switched back though. What would X11 “going end-of-life” entail? Not being distributed/packaged anymore? Is there an official timeline for that or something?
Not that I’m aware yet.
Essentially they’re not doing feature work on the core codebase. I’m not sure if that’s true or not, but the packaging of it wouldn’t be up to the developers but the distro maintainers.
Check out sway. It’s exactly like i3 but for wayland
Wayland reduces bugs and standardizes the desktop, and flatpak makes it easier for distros to include apps without going through the process of packaging them.
This post is FUD bullshit, Wayland and Flatpak are making it easier to run an indie distro.
I’ve been using Wayland for a while, and I’ve seen more bugs with my WMs than in my ~1000 hours of Deep Rock Galactic playtime
Reduces bugs 🤣
Adding 10 bugs to your apps for every bug removed from the display manager
Wayland reduces bugs
As I have to give a few lectures, I can’t say I’m pleased with how screen-sharing or using a projector in the classroom fails almost half of the time and always embarrasses me in front of everyone. I ended up purging the Wayland stuff and going back to good ol’ i3 and I haven’t had a display-related issue ever since.
X11 works, it may not be as sexy or modern as Wayland but it’s battle-tested and just works and for the vast majority of people, excluding Wayland’s bugs, the differences are not even noticeable.
This post isn’t bullshit. The title indicates that we should discuss in the comments. 🙂 I’m not OP btw.
Distros should be free to evolve and fill any amd every niche. Let the rivers of life flow.
It is by the juice of distro that thoughts acquire speed, the fingers acquire stains. The stains become a warning. It is by will alone I set my rig in motion.
People complaining about something opensource not doing what they want it to do: dudes/dudettes, if you want to maintain X11, go right ahead. Or if you want it maintained, pay somebody to do it. But stop this incessant whining about opensource devs choosing a direction you don’t like and pretending it’s the end of the world. This isn’t some faceless, megacorp with closed-source shit you have no control over.
If all the people complaining about wayland either put their energy to positive stuff like making wayland better or making X11 better, this wouldn’t be a problem.
Good thing the world is that simple, you’re completely correct. Nobody who could theoretically prevent something they don’t like is not entitled to their dislike, duh!
That’s exactly what I was I saying! Wow, your reading comprehension gets five stars and a kiss on the check. Papa Wouter must be impressed!
My pet peeve is when people complain someone else’s free labor isn’t being done in the way they’d prefer. First of all, it’s entitled. Secondly, complaining on social media rarely if ever accomplishes anything in FOSS land.
Counterpoint, if all of the people advocating for wayland actually worked on improving wayland to a usable state instead maybe people would actually want to use it.
No one’s forcing you to use it. If you don’t want to, stick to X11. I’ve been testing wayland for a few months now and it’s fine. It does most of I want it to. I don’t need fancy fractional scaling, adaptive refresh rates, or whatever other fancy stuff people complain about that isn’t there. It shows my windows, allows screen-share, and… that’s it. Only thing missing for me is scriptability.
I’m not advocating for Wayland nor X11, just saying to stop shitting on devs who give a lot of free time to write opensource code that none of us have to pay for. All we have to do is be nice - maybe report bugs, maybe maybe donate if we have the means.
There are pros and cons.
Total centralization of the Linux Eco system isn’t good for anyone. But total fragmentation where there’s a million different distros that can all do basically the same thing isn’t good either.
Wayland and Flatpak are great projects though. Love seeing them get more adoption.
Great projects, but far from a finished product.
I mean, they’re never gonna be finished if people don’t migrate to them and work on them. A lot of the wayland issues like “wayland breaks X” is because of the devs of said app rather than wayland itself. Kinda like adobe products and Linux, it ain’t linux that’s breaking them.
Yeah this thread is full of people expecting the new thing to immediately surpass the old, ignoring the decades of development and refinement that went into the old solution.
I get that, I really do, but don’t try and push a product that isn’t usable for everyone to everyone. Sure, whoever wants to use it, they can, report bugs, open PRs, whatever, but don’t push this thing like it’s the second comming to everyone out there. One, not everyone needs the features it has, X11 works fine for most people. Two, it’s not backwards compatible, meaning they’d have to abandon a lot of software that just doesn’t work with it (waypipe doesn’t work all the time and with every piece of software there is).
The transition is rushed, everyone feels that. Why? Because a lot of new features that new hardware had couldn’t be implemented in X11. And let’s be honest, this rushing to switch to Wayland is mostly because of gamers. Regarding a lot of things Linux related, they are the de facto standard that dictates whether somethings get’s changed or upgraded. I’m sorry, but not everyone is a gamer. Most people just need a working PC to do whatever. If you can’t be backwards compatible completely with the old UIs, I’m sorry, but that’s a deal breaker for me and I believe most regular users.
Xwayland is a thing, and nobody stops you from installing Xorg if you wanted. They’re just dropping official support so they can focus that energy to Wayland instead.
Also not all Xorg features should be ported.
I have found Wayland will work for 99% of users who aren’t gamers, all the major programs work well, ironically Wayland has been worse for gaming so far for me on the underpowered laptop, but that’s due to it having to run also through xwayland, which will be a problem solved by Valve pretty soon as they don’t have to worry about Xorg anymore and can make proton work better for Wayland.
do you really expect people, who do this work in their free time out of the goodness of their heart, to release fully finished products that are supposed to work 100% flawlessly right from the get-go? maybe FOSS isn’t the right space for you then.
There are projects that beg to differ. PipeWire, a perfect example. The author thought it wasn’t stable enough even though some distros addopted it as default. He switched to version 1.0 a few months ago.
And I do also use non-FOSS software. I use whatever I like, I don’t discriminate, FOSS or not. Sure, it’d be great if every piece of software was open source, but hey, things are what they are 🤷. DaVinci Resolve is closed source, but there are a lot of things NLE video editors can learn from it.
Wayland is so much better than X. You don’t have to use it but its simplicity means most of the Linux community is going to.
What’s so much better about Wayland than X? I mean, I’m not really a fan of X and the security nightmare that it is, but as a user it’s all pretty plug and play these days. What does a normal user get out of Wayland? Would they even know they’re using it?
I’d love to try it, but it currently won’t work with some software I use, so I haven’t bothered… And honestly I’m kind of confused about how everybody is talking about how amazing Wayland is (and how it seems to suddenly be the one true path for a bunch of distros) when my only experience with Wayland is people talking about how great it is and then not being able to screenshare or whatever… Which doesn’t make it seem great from the outside? That maybe sounds a bit flippant, but I genuinely don’t understand why “normal” people are so excited? I mean, I can see people caring about features like HDR and maybe that’s easier to build into Wayland than ancient X11, but I’d be more excited about the specific feature than Wayland itself which may make implementing these things easier?
Wayland cuts out all of the dead features and allows content to be drawn to the screen more directly. This means that there is a simplified architecture with great battery life.
Do
wmctrl,xdotooland similar work with it, and if not, what are their equivalents under Wayland?Wayland is a protocol so everything is implemented by the desktop.
Other than that, it doesn’t really bring much to the table currently. Not everyone needs (or wants) HDR and many of the other features that I would like to have are still in the works, so… I don’t really see a reason to use it, at least not now.
Support for HDR, variable refresh rate, direct draw and battery improvements sound like a very good list to have, other than the overall leaner build. You personally not caring about it doesn’t change the fact that it’s good to not stagnate when it comes to things like this.
VFR 🤨… I mean, does anyone actually use that? It flopped for video content, I seriously doubt anyone is gonna use that on a PC.
DirectDraw is an MS specific thing, part of DirectX. How does that fit into Wayland?
The second, I would actually LOVE to get in any frame server, X or Wayland, but that will most probably never happen.
Variable refresh rate has become the de facto standard of modern gaming now. They aren’t referring to the direct draw API, but the fact that Wayland does not have extra baggage to draw to the screen through a display server. Wayland just draws to the screen directly, saving time and performance.
VRR is fantastic for games, I really notice the difference and I use Wayland because of it.
The downside to that is (from my understanding) Wayland forces some form of Vsync on everything, so if you don’t have a VRR monitor then games can become very stuttery and have noticeable input lag. There is an option to “force lowest latency” which supposedly allows screen tearing for things like games, though I didn’t test how well it worked myself.
If people are interested in experimenting, then VRRTest is a great utility to see what VRR is doing and to test various settings.
The biggest feature of Wayland for me is mixed refreshrate monitors works OOB. On X this is a pain to get even remotely working and it’s impossible if your monitors aren’t dividable (120/60 works, 144/60 stutters).
This is from my experience something that is starting to be a way more common issue (high refreshrate laptops with 60 external monitors at businesses or high refreshrate monitor for gaming and a smaller secondary monitor for info lookup/discord).
other than that, Xorg does win the “more stable” prize for me, but if I wanted stability, I should’ve become a carpenter.
“I made that chair. It’s stable AF.”
😂😂😂
The biggest feature of Wayland for me is mixed refreshrate monitors works OOB. On X this is a pain to get even remotely working
Literally just plug the monitor and it works. Is this what Wayland people consider hard? No wonder they won’t implement anything remotely complex in their protocol.
Mixed refresh rates do not work because X technically is not doing multi monitor. Both monitors are rendered from the same “screen” that uses one refresh rate. If it’s running at 144hz, the 60 fps screen gets frame pacing issues. If it runs at 60, then the 144hz monitor is slow and gets frame pacing issues, and from most anecdotes and videos I’ve seen, it’s usually the latter and a pain to fix. If you wanted perfect frame pacing on both, you’d have to have the X11 screen set to 8640hz, which I don’t even think can render on modern systems. Wayland, on the other hand, just has multi monitor support built in and actively used. Each display has its own screen and renders at its preferred refresh rate, giving perfect frame rates and frame times for both.
It literally doesn’t work on X11 lol
Then how am I doing it?
It’s been plug and play for a decade but sure.
144/60 works fine for me on X. I only had to disable Vsync for the compositor. Games now run at full 144Hz on my main monitor, and the other two are running perfectly fine at 60Hz.
Though I’m still waiting for the day that I can finally make the jump to Wayland when nvidia support improves (or I have enough money for a new AMD GPU).
If you’re using the latest Nvidia drivers, try it out. I heard support improved dramatically with the latest releases.
Don’t you need a HDR monitor for HDR?
Yes, I believe so.
I don’t even want to know the price. I bought myself a new monitor for Christmas and I doubt it has that.
Mine are all standard as well, usually 10+ years old. I absolutely have no need for HDR, but I get that some people would like to use that.
Here’s the sad truth that Wayland haters hate: Wayland is way more performant and streamlined. X11 is an overly patched mess.
Everytime I had to install a distro, EVERYTIME I had to do some textfile hacking to avoid screen tearing with X11. Turns out in Wayland that is a virtually impossible bug.
Forget about making touchscreens work properly in X11, specially with a secondary screen.
I also remember all the weird bugs that appear in X11 when you have 2 screens with different scaling. No issue at all with Wayland.
Pretty basic stuff in any modern setup.
Wayland performs perfectly on platforms like KDE Plasma or Gnome. I miss no feature. It just requires that some propietary apps realise its potential. And that is what is already happening and will happen throughout 2024.
First of all, X is not a security nightmare. There were 0 cases of someone getting hacked because of X exploit. It’s a FUD.
Now Wayland is a fad (haha). It’s not that much better than X and when it was drafted 10 years ago everyone just ignored it. Over the decade it became clear that X is stuck and at some point it will become obsolete so people started looking at alternatives and Wayland started getting some traction. Over time different tools started getting Wayland support, some people started getting exited about it and a kind of new meme developed where using Wayland meant that you’re ahead of everyone else (just like using Arch BTW). In the end it’s just a nice PR stunt. Ask people what specifically is so great about Wayland and they will mention some obscure features most people don’t need and features that it will have ‘soon’. In the long term the move will hopefully be a good thing but as of now if you don’t specifically need the few features it has you can keep ignoring it.
There are some really major deficiencies in Xorg that aren’t present in Wayland. The main one that made me switch was proper support for variable refresh rate, and the ability to mix and match any fixed or variable refresh rate displays you want.
It’s a super common use case to have a primary monitor with high refresh rate and VRR, plus one or two cheaper monitors that don’t. Xorg doesn’t really support that at all without some really hokey tricks that severely impede usability.
Proper sync support is another one. Yes, you can set tearfree in X but the implementation is crap. You’ll still get tearing in a lot of programs and at least in my experience, it introduces a pretty significant and perceptible input lag, far more than needed to eliminate tearing.
It’s a super common use case to have a primary monitor with high refresh rate and VRR, plus one or two cheaper monitors that don’t. Xorg doesn’t really support that at all without some really hokey tricks that severely impede usability.
I wish Wayland shills would stop spreading this lie. It literally just works. In fact, I’m doing it now on my laptop with a 144Hz 1080p monitor, and an external 60Hz 1440p monitor connected with Thunderbolt, with a dual-GPU setup (iGPU + nVidia, which Wayland doesn’t properly support, yet this is nVidia’s fault somehow even though Wayland compositors run entirely in user space, without interacting with the driver directly).
That’s why it doesn’t make sense arguing about it with Wayland fans. They always find this one obscure feature that X is missing and then claim it’s absolutely essential for everyone to have it. Most people have just one monitor, two equal/similar monitors, a handheld device with one screen or (and that’s the vast majority) simply don’t give a fuck that one of their monitors is working on a lower refresh rate. I’m glad Wayland finally found some traction with gamers obsessed with those things and is being adopted but the constant BS about everyone needing it is getting boring.
Mixed VRR is not an obscure feature for one. Most of my friends with gaming rigs have a primary monitor with VRR and use their old fixed rate monitors as secondary displays. Does it make a massive difference to run fixed refresh rate? No but it is noticeable and nice to have. Windows can do it and I paid for the hardware. Without parity on this kind of stuff, Linux is a hard sell to the people who do care about it.
Does it matter to Joe Schmoe? Probably not, but Joe Schmoe probably doesn’t care about Linux to begin with. You have to go for the tech enthusiasts first before you can get it to the masses.
1.6% of gamers use Linux. 25% of developers use Linux. Typical tech enthusiast is not gamer. Just because in your bubble people use VRR doesn’t mean it’s important to majority of users. Most Linux users don’t care.
With VRR? Xorg definitely did not support this as of a year or so ago without running a separate xorg screen for each monitor which prevents you from doing stuff like moving windows between your displays.
Mixed refresh rates worked okay-ish but VRR definitely did not work well in multi monitor setups.
I believe we’re specifically talking VRR, which for me in Kubuntu did not work properly without switching to Wayland.
Well explained 👍.
It is not a 'fad". Major distros have defaulted to Wayland (Ubuntu, Fedora, Red Hat, Debian, Manjaro etc).
X11 is old and designed for use cases in the 1980s. A lot of features have gradually moved out of X11 into the kernel or into other compositor systems. But the core X11 system is still limited by legacy design decisions and needing work arounds (which are complex to build and maintain).
Wayland is built to be the modern system that is built for current usage and needs. A lot of the benefits are not immediately obvious to the end user - a desktop is a desktop. But desktop interface projects like KDE who build user interfaces are hitting X11s limitations all the time, and a lot of effort goes in to working around X11s limits compared to working with Wayland. Effort spent working to work around X11 is time and work that could have been spent elsewhere on other fixes or new features and innovations.
The push to Wayland is deliberate and necessary, but was not always inevitable. Now that it’s being adopted so widely as the default by big distros and projects it is likely inevitable. It has essentially reached critical mass.
I think a lot of people asking “what’s the point” are not the ones working to build systems and distros at the back end. It’s easy for us as end users to take for granted all the work behind the scenes that make our desktops “just work”. But if you’re a volunteer building a compositor fit for 2024, I can see why it’d be frustrating working around the limitations of a system built for 1984.
X11 has served us incredibly well and is a hugely important project. But Wayland is the way forward.
When Wayland can do and run everything X11 can, without problems, plus everything it promisses it can do, then I’ll make the switch. Till that time comes, I’m sorry, but it’s just not for me 🤷.
Sorry, I used the term “fad” to make a pun on X flaws being a ‘FUD’ (haha). It’s not a fad in the sense that it will soon disappear. What I meant is that the excitement around it is not funded in actual benefits and it just recently became fashionable to support it.
While I don’t think X11 is great, I do not think wayland compositor is made to be easier to develop with. Wlroots had to be made to make things easier for compositor devs.
It’s great on newer hardware, specially phones and tablets. For your 5 year old laptop, it likely is about the same as X11.
What does it do on new hardware? Not a lot of people are running normal desktop Linux on phones / tablets, are they? Which, totally cool if it works better on those things… but I guess I’m just surprised by how much hype there is for Wayland when X just works for me and would presumably just work for most people’s use cases. Like… who are all of these people that are emotionally invested in display servers, and what am I missing?
I mean, 20 years ago or whatever there was always the pain of black screens and X configs… but it just kind of works now in my experience?
For example, Pinetab 2 was developed and tested with Wayland and is more stable on it. Plus way better touchscreen support.
Sure, if you call “simplicity” to literally not doing anything so that every coder has to implement the graphics stack on every program on their own.
Well no, its handled by the desktop and libraries.
Flatpak doesn’t conform to the XDG home directory, and that upsets me. Also we have an ongoing dispute between SI and IEC units on their GitHub. But I like it otherwise.
The way the flatpak devs responded to the xdg base dir request made me not ever going to use flatpak again, fuck them.
What did they say?
Yikes that’s not a good look, why dig in so stubbornly?
There are other interesting ones here:
https://wiki.archlinux.org/title/XDG_Base_Directory
The one for steam turned into a bunch of memes because steam hasn’t even acknowledge it lol.
https://github.com/ValveSoftware/steam-for-linux/issues/1890
Oh, no, it’s Patrick (tingping). He is very stubborn and doesn’t listen to reason. https://github.com/flatpak/flatpak/issues/5504
I really wished that he didn’t participate in the XDG problem, but he did. Then the IEC issue is probably also be screwed in the end.
I didn’t know flatpak was using MB instead of MiB, ever since I moved to linux most apps I’ve used report MiB instead.
Edit: I checked my CLI tools because the guy said that CLI tools are all over the place, the only one that doesn’t use MiB is lf.
Edit2: I lost my shit when I checked the profile of patrick and the first thing in the description says gnome developer, holy shit this can’t be lmao.
Not doing that is the whole point of flatpak. XDG_HOME is a bad design because it leads to a giant and hard to sift through swamp of mixed files, with no separation in terms of tidyness and security whatsoever.
Flatpak packages still suck at integration without breaking something in the core app. They’re really great for bleeding edge and cross distro support tho.
Wayland still can’t do all the cool tricks X11 can, so it’s not like it’s really being forced upon anyone beyond X11 losing on potential major updates which is unlikely.
DEs are willing to switch to Wayland given that it is either equal or superior to X11 which is still not the case for several scenarios and applications.
Exactly my POV. Do all the things X11 can, and I have no problem switching whatsoever.
Why did no one had any issues switching from PulseAudio to PipeWire? Because it was simply better. It could do everything PulseAudio could, plus a lot more. It was backwards compatible (with plugins of course) and there were practically very little issues with it at the point at which distros and users decided to switch. It was a finished product.
Speak for yourself, I’ve had enough issues with both PulseAudio and PipeWire to abandon gaming on Linux which is a shame.
What exactly was wrong with PipeWire and gaming (Steam I presume)?
I don’t game, but I do music on Linux, use Ardour… sure, it requres some setting up, but far from anything super complicated.
Ok, but nobody explained what the equivalent of “ssh -X” was supposed to be with wayland.
waypipe
Oh, cool. I’ve been looking for that for ages. Thank a lot!
Does this work well with X11 -> Wayland communication? Or do both computers need to be Wayland?
after a brief glance it looks like it, but that’s the same case as x over ssh. otherwise there’s things like vnc that wouldn’t care what each side is running
It doesn’t exist as far as I know.
Waypipe
It’s such a niche feature that I bet most people under 30yrs never heard or used that it’s become too cringey that everyone keeps mentioning it.
But there’s the solution already mentioned.
I’d just like that some people would look a bit at themselves and realize that almost nobody wants or cares about that single weird feature. There are many remote desktop solutions more known to end users that need that kind of interaction.
Actual Unix users care. Maybe people that just jumped ship from Microsoft don’t, but I think that’s just because they don’t know what’s possible and how convenient it is.
I have also jumped ship from MS, but it is actually a cool feature. I don’t use it that frequently, but a few times a month, yeah.
I suddenly have the urge to daily drive Hannah Montana Linux
To devils advocate a little in general with this topic: For wider spread adoption, Linux kinda needs to adopt around more standards. If you put yourself in the shoes of the average windows or Mac (even iOS/Android) user; it’s an overall standardized experience.
Linux now, is mostly a choice of DE and package manager. I still absolutely want distros like arch and Gentoo to still exists as they are.
Windows and Mac don’t have standards; they’re single solitary stand alone monoliths. The user experience is the same in their walled gardens because they are the same, not because those systems embrace standards. In particular Microsoft’s lack of standards has been a point of pain for Linux and FOSS users for decades. Linux has actual standards and that is exactly why there is so much diversity. That diversity would have crumbled into chaos long ago if the Linux community did not embrace standards.
If Windows users had to deal with the dependency issues, it likely would’ve never taken off. That’s kind of the problem I’ve seen around various Linux distros, though I wager it’s gotten a lot better in recent years. For the record, I’ve been out of the Linux game for a good 6 years, and I barely ever boot up my computer much. I’m able to run my business completely off my phone (except tax season), and I haven’t made the earnest effort to get back into it due to time constraints.
Man…we’ve been saying that since '99…
I mean it has gotten a lot better. Dependency hell is mostly a thing of the past. If you were around back then using it then you should know the suffering we all went through to get ANY sort of usability out of it. Half the time it wouldn’t even fucking work at all due to some weird hardware you had, or you were limited to terminal only because XFree86 didn’t know what to make of your video card (it was a time of cheap shitbox Pentium MMX/Pentium II/Celeron machines, some of which came in cow print boxes). It sure has come a long way from my perspective.
The several distros is a thing of sheer beauty. It’s like the meritocratic free market – everyone can participate and the only way to win is to make something better than anyone else.
I don’t mind Wayland but I sure hope flatpack will not become the default way to distribute packages. Most packages I tried so far didn’t work. I just avoid it now.
That’s strange? I’ve never come across a single broken Flatpak across multiple computers with Linux installed. Do you have examples of broken Flatpaks?
Nope, I don’t remember and after it happened couple of times I just started avoiding it.
I don’t use it at all, I just repackage stuff that I need for my distro’s package manager… if they’re not in the repos.
