jack

joined 1 year ago
[–] [email protected] 12 points 1 week ago (8 children)

Memes should be entertaining and/or funny. This one is neither :(

[–] [email protected] 1 points 1 month ago* (last edited 1 month ago)

Sooo where's the video? Can't find it anywhere

[–] [email protected] 2 points 2 months ago* (last edited 2 months ago) (2 children)

Yup, the other side is pretty counterproductive with saying the project is dehumanizing etc. They're absurdly exaggerating.

It wasn't just a report tho, it's a PR that could've been merged with a single click

[–] [email protected] 4 points 2 months ago* (last edited 2 months ago)

Open mindedness is a key factor for success (especially in open source). Inclusivity demonstrates open mindedness. The fact that the lead dev goes out of his way to prevent such a minor change (it's not even like people demanded a strict CoC or something) is a bad signal

[–] [email protected] -2 points 2 months ago* (last edited 2 months ago) (7 children)

Open mindedness is a key factor for success (especially in open source). Inclusivity demonstrates open mindedness. The fact that the lead dev goes out of his way to prevent such a minor change (it's not even like people demanded a strict CoC or something) is a bad signal

[–] [email protected] 16 points 2 months ago (1 children)

Ask him to do 500 lines and he will never look at it, making you wait forever

[–] [email protected] 3 points 2 months ago

As per my other comment:

Do your latex work inside a distrobox and you're fine.

I'm not sure if you can layer another window manager on top. You may have to create a custom image for that

[–] [email protected] 3 points 2 months ago* (last edited 2 months ago) (1 children)

Basically installing packages. You're fine if you default to using

  • flatpaks for gui apps
  • brew for cli programs
  • distrobox when building from source or when you need good control over the package environment (e.g. when installing a latex editor and only the latex packages you want)
  • layer packages on host with "rpm-ostree install" when the program needs tight integration with the host (e.g. VPN software)

Also, you shouldn't edit files in /usr, but I've never run into that limitation. You can still edit other top-level directorys like /etc .

That's about it.

[–] [email protected] 2 points 2 months ago

Just use brew for non-gui programs. Really easy. It's the recommended way by the ublue devs and should be pre-installed

[–] [email protected] 8 points 2 months ago (2 children)

Biggest benefit for me is automatic updates in the background which are also safe. On a normal distro, if your pc shuts down for whatever reason during kernel updates you have an unbootable system. That can't happen on bazzite

[–] [email protected] 3 points 2 months ago (5 children)

The solution is to not be cconfident and remain open minded. You can switch any time

[–] [email protected] 1 points 2 months ago

Here's another comment with more detail

1
submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/[email protected]
 

UPDATE: I found this issue explaining the relicensing of rust game engine Bevy to MIT + Apache 2.0 dual. Tldr: A lot of rust projects are MIT/Apache 2.0 so using those licenses is good for interoperability and upstreaming. MIT is known and trusted and had great success in projects like Godot.

ORIGINAL POST:

RedoxOS, uutils, zoxide, eza, ripgrep, fd, iced, orbtk,...

It really stands out considering that in FOSS software the GPL or at least the LGPL for toolkits is the most popular license

Most of the programs I listed are replacements for stuff we have in the Linux ecosystem, which are all licensed under the (L)GPL:

uutils, zoxide, eza, ripgrep, fd -> GNU coreutils (GPL)

iced, orbtk -> GTK, QT (LGPL)

RedoxOS -> Linux kernel, most desktop environments like GNOME, KDE etc. all licensed GPL as much as possible

view more: next ›