How did Your Party do?

Fully agreed.

If you’re big enough, interoperability still costs and provides little benefit. Vendor lock-in is also a thing between distros.

https://distrowatch.com/search.php?origin=Israel shows no results.

Here‘s your list of Israeli FOSS https://github.com/lirantal/awesome-opensource-israel

It’s not in Red Hat interest to accommodate other package managers.

What software for example?

Exactly. Linux is often held high as an example of how to realize tech sovereignty. Most of it is repackaged work by Red Hat. That’s still a dependency. If the US made a law restricting export of source code, this would have immediate consequences to Linux use in Europe.

For streaming https://yarrlist.net/

Sure, that’s the theory. In practice code review often looks like this:

• a quick glance to see if the code plausibly does what it claims for longer patches
• A long argument about some stylistic choice for short patches

In other words – people were barely reading merge requests before. Code reviews have limited effects as well. You won’t catch all bugs or see if it actually works just by looking at the code. Code reviews mainly serve to spread knowledge about the code among the team. The more code exists in a project, the harder it is to understand. You don’t want huge areas of code, that only one person has ever seen.

Project managers don’t necessarily talk to angry customers directly. They might also choose to chase more features instead of allocating resources to fixing bugs. It depends on what the bosses prioritize. If they want AI and lots of new features, that‘s what they will get. Fixing bugs, improved stability, better performance, etc. are rarely the priority.

Realistically what happens is the code review is done under time pressure and not very thoroughly.

Make real backups. Ideally make two or more

• a full disk backup with SuperSuper
• A Time Machine Backup on an external drive

The likelihood of making your machine unusable for a while is non negligible.

Mac

If you want to dual boot with macOS, do some research. Boot loaders and EFI can be tricky.

Holding alt after pressing the power button gives you the option to choose the drive to boot from. Holding cmd + R after pressing the power button allows booting into recovery mode. It allows you to partition and format your internal drive and reinstall macOS.

You can install a newer version of macOS than is officially supported using OpenCore Legacy Patcher.

FOSS principles

Intel Macs often have Broadcom WiFi chips, that need proprietary software to work. As a noob, you should got with a distro that makes it easy to install these or does it automatically for you.

You likely also want to play some video files, so you will need nonfree stuff.

Distro hopping

Install to an external drive or Virtual Machine. You can do that on your existing macOS with VirtualBox for example.

similar to Windows, macOS, customizable

Even the desktop environments, who claim to be macOS like (Endeavour, GNOME), have at best a superficial similarity. Don’t expect a macOS replacement. All desktop environments are different from macOS.

beginner distro

Fedora and SuSE are not beginner friendly. Lots of Linux distros use the same marketing terms of easy to use, powerful, efficient, etc.

Start with Ubuntu or something based on Ubuntu like Mint.

Cinnamon, KDE, and Gnome are all good desktop environments for beginners.

The LaserDisc version of DS9 is available on archive.org, seasons 1 to 3. The aspect ratio is wrong for me when watching it in the browser. Download the files directly and watch locally.

Live long and enjoy :)

Smartphones have been taking HDR photos for years. Of course supporting HDR screens is a must.

What’s your strategy for picking compatible hardware?

Maybe the license makes it easier for the developers to be hired for contract jobs, that build upon it.

Why? BSD has an equivalent to coreutils with BSD license.

FreeBSD and the other BSDs are doing pretty well with permissive licensing. They have done a lot of important work that also ended up in Linux.

What sometimes happens is their code is forked, and then published under GPL. Meaning the original project isn’t given back to.

You only need to provide source code to your users. There’s no need to provide a public git repository to the world.

You can fork GPL software and sell it. If one of your customers asks, you can send them a copy of the source code on a DVD. This is all the GPL requires.

VMs don’t show you if your hardware is well supported.

The better name would be Linux/systemd/Wayland/KDE.