[-] LeFantome@programming.dev 10 points 1 year ago* (last edited 1 year ago)

Here is an argument that some of the grumpy old men clinging to Xorg may understand.

It is 2003 and all the cool kids are moving to this new web browser called Firefox. But every time you try your favourite websites in it, you find stuff that breaks. So back to trusty old Internet Explorer 6 you go. Call me when it works you say.

Wayland is like HTML. Wayland compositors are web browsers. And yes, all these “modern” web standards are all implemented a little differently or maybe not at all in some browsers. And, annoyingly, a lot of real world websites still work better in Internet Explorer 6 than in any of these supposedly “modern” browsers.

But, as with the web, it will not be long until all websites (Linux desktop applications) will be written to use the modern standards and will work well, and pretty much the same, in all browsers (Wayland compositors).

And, while there will still be websites (Linux desktop apps) that work better in IE6 (Xorg), most people will consider those sites broken and will probably not use them. Alternatively, you can run your browser (compositor) in compatibility mode (Xwayland) for those sites.

You can keep using Internet Explorer if you want. Many people held on for a long time. Just know what your advocacy sounds like to people that have moved on to Firefox and Chrome. Pointing at your corporate website that looks wrong in Firefox will not impress them. And understand that you will not be able to hang on forever. Well, unless you want to be stuck in a tiny corner of the web that still works on your browser. Most websites will stop working on Internet Explorer at some point.

[-] LeFantome@programming.dev 10 points 1 year ago

How is a guy playing to 100 people in a field for free getting this much national press?

[-] LeFantome@programming.dev 10 points 1 year ago

Shortcut is much simpler, in both the good and bad ways.

[-] LeFantome@programming.dev 10 points 2 years ago

It is not paranoia of you your risk assessment is accurate. It is just awareness.

[-] LeFantome@programming.dev 10 points 2 years ago

Just because he doing all that as well doesn’t mean he won’t get to it. Destroying things is easy work. Sometimes all it takes is not doing other things.

[-] LeFantome@programming.dev 10 points 2 years ago

I think if Trump loses the election, it will hurt Pollievre as well.

[-] LeFantome@programming.dev 10 points 2 years ago

If it runs under WINE, it will probably be higher performance and of course integrates better into the rest of your system ( eg. files ).

If it does not work under WINE, it will probably work in a VM. So, depending on the app, this may be the only choice.

Apps that depend on talking to specific hardware ( including the GPU ) do not always work in a VM.

So, it depends…

[-] LeFantome@programming.dev 10 points 2 years ago* (last edited 2 years ago)

In what way?

The binary formats are not compatible, not even the format of the files themselves. Linux uses ELF. MacOS uses MachO.

True, macOS is more or less POSIX at the base but the API Mac applications are written to is not that at all ( Cocoa ). GNUstep exists for a reason. Sadly, it is not very mature. It is certainly not a trivial undertaking though as there have been a number of attempts over decades and nobody has really pulled it off.

The Win32 API on the other hand has largely been implanted on Linux. A few Win32 APIs are even being added to the kernel.

Going the other way is easier. You can port POSIX stuff to macOS fairly easily.

[-] LeFantome@programming.dev 10 points 2 years ago* (last edited 2 years ago)

Why does every mention of Rust have to spawn these comments?

The story right after this one for me is how KeepassXC is porting to Qt6. I bet nobody has knee-jerk responded to that story bitching about the fact that they mentioned Qt. It is just the anti-Rust zealots that do this.

This article talks about the problems they were trying to solve, the tools they chose, and how those tools solve those problems. What is wrong with that?

Are you offering up informed commentary countering why you would have made different choices and why?

You do not need to attack every mention of a technology just because it threatens your historical preferences.

[-] LeFantome@programming.dev 10 points 2 years ago

I do not recall other distros failing to update due to GPG key issues but it has happened to me on Arch distros many times. It is the biggest pain when converting from something like Manjaro to something like EndeavourOS as well.

I really do not understand why this cannot be fixed.

[-] LeFantome@programming.dev 10 points 2 years ago

I am trying to think of how to respond to this without being a jerk.

Let me skip to the end. Until very recently, I thought of Manjaro users as innocents that just did not understand the risk. Like islanders living next to a volcano that had never erupted in their lifetime.

I still view most Manjaro users that way. Manjaro defenders though I now think of as dog owners whose animals have bitten multiple times. When told, the owner insists that “my dog would never do that” or “if it did, you must have done something wrong”. I am done arguing with those people. All I can do is warn others that this dog has bitten several of us and you may not want to enter that yard. If you do, who knows, the dog may be friendly. Or not. Again, all I can tell you is that many of us have scars. Use that information as you will.

Most “Manjaro detractors” I have encountered have years of experience with both Manjaro and other Arch distros. Their tales come from experience. When they share their cautionary tales, there are often Manjaro defenders whose best defence is just to deny that what the “detractors” are saying ( about their own experience ) is real.

My core question for the defenders would be, if it is our fault, why do we only encounter the problems on Manjaro?

Let’s go through the bullets above one by one:

  • I never did that on Manjaro. I probably do it more on EOS. Why only problems on Manjaro?
  • why does my lack of knowledge of how the AUR works only break things on Manjaro?
  • this bullet is the best. It admits that Manjaro has repeatedly broken things but we should not hold it against it. Literally this is saying that “Manjaro breaks things” is wrong because, while it does, we should just get over it. Hilarious.
  • how does attacking the “detractors” address the claim that Manjaro breaks things?
  • how does attacking the “detractors” address the claim that Manjaro breaks things?

I got in a lengthy back and forth with a Manjaro fan the other day where I repeatedly related the ways that Manjaro used to break on me and how that does not happen for me on vanilla Arch or EndeavourOS. They just kept coming back telling me that it could not have happened and, if I thought it could, that I did not understand how the AUR works. It was insane. Basically, this guy could not follow what I was saying to him. His response to his inability to understand the scenario that I was describing was to insult my intelligence and expertise.

Look loser. I don’t care if you believe me that your dog bites. I will continue to warn people and they can decide if they want to risk it or not.

[-] LeFantome@programming.dev 10 points 2 years ago

I guess I should hold off on upstaging my systems. There are going to be a lot of deals.

view more: ‹ prev next ›

LeFantome

0 post score
0 comment score
joined 3 years ago