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

There is not hypervisor. So, no hypervisor to update.

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

I would have gone with GrubCraft but awesome otherwise.

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

There is no stauncher enemy than a friend denied

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

I have 4 kids. Comments telling me to put their groceries and hockey gear in a basket are hilarious.

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

I assume you mean The Linux Foundation.

While the LF is US based, the real “product” is the distro and you can choose a non-US distro. My distro of choice is based in Spain.

And, if needed, the kernel could be forked to anywhere in the world without disruption.

Many core programs are built primarily by US firms, like Red Hat, but even OpenBSD relies on many of those. Same story with the forking. OpenBSD maintains some of this themselves (like X11).

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

Permissive licenses are trending in popularity vs copyleft. As a “newer” ecosystem, the Rest-dev culture skews towards permissive.

Why are permissive licenses popular?

Most Open Source software is written by companies.

“Permissive” licenses offer more flexibility and compatibility while minimizing future legal complications. You can replace the word flexibility with the word freedom if you wish. By compatibility, I mean it can be combined with code using other licenses. So no “we cannot combine ZFS and Linux” type problems.

MIT offers the absolute minimum of legal footprint and maximum compatibility.

The above are attributes companies value.

On the other side of the “freedom” front, licenses like MIT guarantee all of the “4 freedoms” that groups like the Free Software Foundation talks about with adding an restrictions on the freedoms of others.

So, why doesn’t everybody use MIT? The patent guarantees in Apache 2.0 are useful if you are ok with the added complexity (still permissive but more legalese).

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

I do not want Flatpak to replace distro packages.

I use both pacman and apk and they are both far better package managers than Flatpak is. Apk 3 is awesome. And I do not want sandboxes for native packages.

The role of Flatpak is as a distribution method for app developers to target Linux as a platform with a single build. It is a place to get things that may not be in my distro repos. It can be a method for commercial distribution. It is the cure for the “fragmentation” problem that makes it difficult to develop software for Linux.

I hate snaps but snaps could actually be used to replace packages. You could distribute GCC as a snap. In its current form, Flatpak is only targeting GUI applications

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

No.

Microsoft maintains what is essentially the “real” version of Mono within their official .NET project. It is up to version 8.

The version of Mono represents by “The Mono Project” still targets .NET Framework ( stuck on version 4.x for years now ). Microsoft does not care about the real version, nevermind the Open Source replica.

What Microsoft is “donating” is pure legacy. It is a good fit for Wine though.

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

You are completely correct. The good news is that the “official” .NET is Open Source now and far better than the “Mono Project” ever was.

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

Linux being more popular means more applications of higher quality. I guess this does not matter to you. For those of us that would prefer more high-quality applications, Linux popularity matters.

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

For many uses, Wayland has feature parity now or is even the superior option. That is how it can be the default on so many systems ( including RHEL9 as per the article ).

Compositors that do not provide the features that uses want will fail to compete ( what you mean by become useless I assume ).

That said, different users will want different things and, unlike X, Wayland allows competing compositors to address different communities. Some compositors will lack features some users want while offering features that other users need. A composite targeting embedded use cases may not need multi-monitor or fractional scaling features for example. A security focussed option may think that global hot-keys and external lock-screens are anti-features. I think the Wayland world could be quite interesting.

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

Waypipe addresses forwarding. The major Wayland compositors support either RDP or VNC already I believe.

view more: ‹ prev next ›

LeFantome

0 post score
0 comment score
joined 3 years ago