It is not about how well it works. They can certainly disagree about that.

The problem was that they clearly have no idea how it works and “warned” people about a bunch of things that will not happen.

If posted a comment about Linux and told you not to use it because it would cause your hardware to disintegrate, the issue is not my level of Linux advocacy. The problem would be that I am peddling actual falsehoods.

This is a dramatically misinformed comment. You have clearly never used Distrobox.

1. The first bullet is the worst. This is like saying that Flatpak will break your host. It will not break the host OS. Learn what a container is.

2. It is not tools on top of tools. It is tools in a container that you can optionally create entries for in your app menu. Apps in the container execute directly on the host kernel in the container. If you are in a shell, you are either in the container or out and the full environment will reflect that.

3. It is not for “new users”. That said it dramatically simplifies many intermediate ones and make some advanced things possible. Once again though, there are no “stacks on stacks”.

4. The exact opposite. Containers do not change the host. If something goes wrong in the container, you can purge it completely without impacting the host.

In fact, one of my core uses for Distrobox is to keep my host system clean. I use Distrobox to setup dev environments, to try out new software, to work around Distro constraints, and a host of other tasks. It is great.

There seems to be quite a fundamental misunderstanding of what a container is. Everything runs directly on the host kernel. Apps outside the container run on the host OS and do not interact with the container. Apps in the container run in the environment inside the container. The only interaction apps in the container have with the host is the kernel, the filesystem, and via servers like Wayland, Pipewire, and XDG portals.

The entire point of a container is to create an application environment that looks exactly like an application expects regardless of system it is running on. It is clean and consistent between deployment. This is the exact opposite of what the above comment implies.

In practice, it “feels” like apps in Distrobox are running native on the host OS but in fact everything above the kernel is running inside the container and each container is distinct from the others.

The “example” is totally wrong. GCC is either on the host or it is not (from the host). GCC is either in the container or it is not. They do not interfere with each other. They do not even share C libraries. However, the can see the same source files.

Distrobox is absolutely nothing like Homebrew. Homebrew is a package manager. If you are using a package manager in Distrobox, it will be the one intended to work with whatever distro you are running in Distrobox. This is a fantastic illustration of the confusion of ideas at work here.

If you have to compare Dostrobox to something, compare it to Flatpak.

The most of countries likely to invade Canada is as follows:

• the USA

Nobody else could manage a land assault on North America. Coming in from the arctic would be almost impossible.

Invading from the west or south means the US is in the way. And the US is unlikely to tolerate an invasion to the continent anyway (unless they are involved). And where is an invasion from the east being staged? Europe?

In practice, Finland and Poland are the greatest protection against Russia as they are very much in the way and would trigger all of NATO.

Many European counties have very credible defence industries. From what we have seen in Ukraine, NATO (even without the US) has both a technological and tactics advantage against Russia.

We are also seeing that warfare has changed. He who makes the most drones and cruise missiles wins.

And Europe could massively outspend Russia, again without help from the US.

Germany has massively stepped up their military spending. If they had to, Norway to completely fund a NATO war against Russia on their own.

The only thing the US really brings to NATO these days is their nuclear arsenal. But again, Russia has shown that their “superiority” in this area is useless in practice. It will not help them in a war with Europe.

The only way that Europe loses against Russia is if the US teams up with them. This used to be an insanely unlikely outcome but….

Did you mean USSR? I assume so but it is just “not obvious” enough that I may be missing out on what URSS means.

I see that you have responded to multiple people this way.

I have never heard of you but your responses lead me to believe that they are correct.

That would be a plot twist. Far more likely is that they go in on it together.

I used to think the problems with Manjaro stemmed from Arch. The I tied EndeavourOS and I thought that EOS was fixing the Arch problems.

Then I tried Arch and realized that all the problems are the result of Manjaro. Arch does not have them. None of the other derivatives have them either.

Manjaro is a Trojan Horse.

They may team up

It has gotten better in Wayland. I am looking forward to the near future when we can finally stop appending “on Wayland” to everything.

You should use what you like.

COSMIC may offer a middle ground if you did want to try something else though.

And KDE is very configurable. It does not have to look like Windows.

The GNU projects that people actually use are primarily hosted, maintained, and developed by Red Hat (IBM). They are the primary code contributors. Not just GPL, GNU specifically.

This is just a fact.

https://sourceware.org/ (Previously known as sources.redhat.com)

There is more permissively licensed code in most Linux distributions than there is GPL code. Not only is that permissive code not being “stolen” by “mega corps” but the majority of it is corporately funded.

Again, just facts. All pretty easy to verify if facts matter at all to you.

What part did not make sense? Just that the facts do not agree with your opinion?

The comment I responded to was stating things that sounded like facts that are not at all supported by the evidence. And if I ask for some, I am pretty sure the cherry-picked examples will be mostly companies “stealing” projects that they wrote to begin with.

The thesis that permissive licenses result in less Open Source code is wrong. In fact, they lead to greater corporate participation and employees write more code than unsponsored individuals. That is what the evidence shows.

Use whatever licenses you want. Not wanting companies to use code you wrote is a totally valid choice. But you should not have to misrepresent reality to convince other people to do the same.

You are in luck. COSMIC launches in 3 days.

I am also interested to see what kind of adoption COSMIC gets. From the comments I have seen, I looks like it may pull-away a fair number of GNOME users.

Nor sure that COSMIC calendar will have all the features you want. COSMIC is a pretty good base for GNOME apps though. It does not have to be either / or.

If you ever want to try Wayland, check out LabWC.

I am also loving Niri

Sort of.

Everything is Wayland compatible but there is no XFWM for Wayland. So, you use a Wayland compositor like LabWC with the rest of XFCE running on top of it. This is the default XFCE config on SUSE Leap for example.

XFCE is not quite as far along on portal support as GNOME or KDE though. Depending on your use case, you may still prefer running on Xorg.

You can run the XFCE apps on any Wayland desktop.

Hundreds of billions of years should be sufficient t

Having the original UNIX source code with fully preserved timestamps?

Even if this happened, you cannot count on it. Trump or someone like him will take them back.

If you build and service Gripens in Canada, you can count on those jobs.