[-] LeFantome@programming.dev 4 points 8 months ago

You are wrong. I doubt I will change your mind.

  1. There are many, many, many more companies using Linux without giving back than there are for BSD. And not just “using it” either. Practically the entire embedded universe is one giant GPL violation.

  2. Linux is not “true” GPL anyway, so it is a poor example for how the GPL impacts success.

  3. The companies that build businesses on FreeBSD tend to give back. There are many examples, the biggest being Netflix.

  4. The classic example of a company not giving back is Sony and even that is wrong.

  5. People choosing a BSD license value different things, rendering your entire premise meaningless for them and your framing of “the problem” inappropriate.

I do not want to get too deep into Sony. But let’s acknowledge that they first tried to ship Linux on PlayStation. They had to stop. Why? Well, it was not because people tried to copy the operating system. It was because people used it to circumvent other protections to copy proprietary games. The problem was not with Sony’s ethics but with those of “the community” and the lack of respect “the community” had for the concept of copyright.

So, Sony switched to a FreeBSD base and they no longer share that code. True.

However, Sony does contribute to BSD. And Sony is a significant contributor to Clang/LLVM and they do share their work freely (even though the license does not require them to). The FreeBSD project benefits from this as Clang is the system compiler. I benefit from this as my Linux distro also uses Clang as the system compiler.

The BSD license is “free software” and provides all “4 freedoms” touted by the FSF. It protects your rights with regards to the code you have and are using. It does not give you guaranteed access to FUTURE code that you do not write. Those future contributors are free to choose their license. You know…freedom.

BSD lags in features, particularly hardware support, because it has fewer users and therefore fewer developers. That is mostly an accident of history and not, in my view, due in any way to the license. Look up the BSD lawsuit that was happening when Linux appeared. If your argument for the popularity of Linux is the GPL, why did Xorg become the dominant window system instead of something GPL based? Why did Rust, Swift, and Zig appear on LLVM instead of GCC?

Anyway, I could write 100 paragraphs and not change your mind. You certainly have not changed mine.

[-] LeFantome@programming.dev 4 points 9 months ago

You do not need to understand anything about X11 vs Wayland. Use whatever your distro of choice defaults to.

Wayland is the future. Every Linux desktop user not fighting hard to avoid it will be using Wayland in 2 years. The majority are already.

Wayland and X11 are both protocols. They are a way for graphical applications to talk to a “display server” (your graphical desktop).

X11 was invented in the 80’s. Until recently, there was essentially only one surviving implementation on Linux—something called Xorg. While Xorg was the display server, you had to add something called a “window manager” to control what your desktop would look like and how windows would behave.

While Wayland essentially does the same thing as X11, it was built to quite a different set of design criteria. If you have not been part of the history, it is not worth knowing about. Security is one of the big improvements.

Perhaps the only detail worth mentioning is that the display server and window manager functions have been combined in Wayland into something called a “compositor”. So while everybody was using Xorg back in the X11 days, there are many competing compositor implementations in Wayland. They differ not just in how they manage windows but also in how them implement many other details like how to take screenshots, manage multiple monitors, or handle scaling. There are a set of standards that define this behaviour. It is a bit like the web where you have different web browsers and web servers but the same web applications work on all of turn (which perhaps some small differences).

The two systems both “do the same thing” and are quite different at the same time. If you use one, switching to the other may seem painful as things that worked may not anymore and even things that still work may be done differently or require quite different knowledge. Not many people switch from Wayland to X11 but anybody that used Linux 5 years ago has had to switch from X11 to Wayland (or feel pressured to). Not all of them are happy about it. Some of them rely on workflows that Wayland does not yet or many never support. These people consider the switch to Wayland a really big deal which is why you hear about it so much.

But, if you already use Wayland, ignore it. Everybody will stop talking about it soon as almost everybody has switched. The majority that have not switched are using popular desktops like Cinnamon or XFCE that have also not switched. They have not switched as they want to make the transition very seem-less for their users. Which also means you do not have to think about it. One day they will move you and hopefully you will not notice. Or, even better, it will seem like a bunch of new features in a new release.

[-] LeFantome@programming.dev 4 points 9 months ago

What did you replace Xorg with 10 years ago?

[-] LeFantome@programming.dev 4 points 9 months ago

Of that happens, we cannot be forced into an election. Which means Carney can largely ignore PP for a couple of years.

[-] LeFantome@programming.dev 4 points 10 months ago

Well, I don’t know Fortran 66. So, obviously step one is having an LLM convert it to Python for me. /s

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

Agreed. If something happened, Greg would certainly take-over at least temporarily. Then the LKML would fight over succession like they fight over everything else. It would take too long, it would be dysfunctional, at least one person would quit the project but they would settle on a perfectly workable solution in the end. And it would evolve from there.

There is a whole hierarchy of ownership in the kernel. It is not entirely explicit. It can be quite fluid. It is not as dire as the article states.

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

In an alias like this, running pacman first has the advantage that the true Arch packages install completely before any AUR packages that require slow downloads, package compression, or long build steps.

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

You are 90% of the way there.

Just keep your system up to date (update packages weekly maybe) and you will be fine. The system mostly manages itself.

I recommend installing both the current kernel and an LTS kernel. If you ever have a problem with a driver or a filesystem or something after an update, just boot into LTS and you are back up and running.

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

The only way to fix Xorg is to break org. It requires a redesign.

The Xorg devs chose to do that by starting a separate project. The breakage has been in Wayland, now maturing, while Xorg was left stable. Xlibre wants bring this disruption to the X codebase itself.

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

MPV is a much lighter video player. Try that.

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

I was trying to think of the oldest hardware I have run modern Linux on (probably an old Pentium II) when I remembered that I used to run SLS on a 486 (33 MHz, 4 MB of RAM).

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

To be clear, you still still be able to run 32 bit binaries on a 64 bit kernel. So, there will be no more kernel support for Pentium (in 5 years or more) but you will still run i686 userland code. I do not see this changing for a very long time.

view more: ‹ prev next ›

LeFantome

0 post score
0 comment score
joined 3 years ago