Shares aren’t necessarily voting shares, but I don’t know how that works and if it’s even relevant for the private Valve corporation.
So maybe Gabe Newell does have full control over Valve, or he might not.
It’s definitely interesting that it’s only 25%.
Yes, NixOS does need quite a bit of RAM while rebuilding (~1GB) and takes lots of storage because it keeps older generations (similar to OS snapshots) around.
Otherwise NixOS isn’t any more resource intensive than other OS. Anecdotal experience, but my NixOS system boots faster than Fedora Atomic with the same window manager and packages installed.
In any case, I’ve been using NixOS, Fedora Atomic and OpenSUSE MicroOS on my T480s without problems, so OP will be fine with any distro.
Hyprland and sway are the most feature complete tiling compositors I’ve tried. But since I strongly prefer dynamic tiling, there’s not much of a choice. River tiling is the best in my opinion. Sadly it doesn’t support moving workspaces between monitors, as each monitor has its own set of workspaces, which is a deal breaker to me.
In general I strongly prefer Wayland over X11, as I’ve found Sway to be a better experience than i3 + picom for many years (not having to disable the compositor while gaming, better multi monitor support, etc), but having to switch to wayland-native tools is necessary coming from X11 wm’s. For DE’s that’s not an issue.
Yes, with Vaxry being banned from contributing to wlroots, hyprland development won’t get easier. At the same time I’d say wlroots and hyprland are largely feature complete, so not being able to contribute might not have a large impact on hyprland.
Agreed. Their discord has been full of inconsiderate jokes and memes for a long time. It’s not untypical of many edgy internet communities but it being directly associated with a project isn’t a good look.
I definitely wouldn’t want to get involved with such a project, altough it is a good piece of software and I don’t see their behaviour influencing the popularity of hyprland.
It still works for private instances. The moment a public instance makes enough requests to reddit, they block it.
I’m running libreddit on my home server and access it through wireguard. Never been rate-limited. It’s the only thing I still use Libredirect, since most platforms ban third-larry frontends.
Yes, I’ve no problem with your position on copyright and many institutions do many bad things. My issue js with misuse of terms with a fixed meaning, i.e. open-source. Having different people use a single term in multiple ways makes it so much more difficult to understand each other and enables bad actors to rile people up against each other.
A tame example is “stable” Linux distros, where "stable"can mean package versions stay the same (besides bug fixes), and then people come and say their Arch Linux never broke, so it too is “stable”.
Why wouldn’t it be open-source. It’s right there in the name: the source is open.
In the context of criticism of how copyright works I understand the above sentence, but using a well understood term differently still annoys me enough to write lengthy comments.
PS: I do hope lemmy implements a way to add copyright notices to comments like it allows for setting the language of posts. It could be implemented in a less noisy way. People who don’t care about a license ignore it anyway, while people who do care would likely find it without much trouble.
The license you’re attaching to your comments uses copyright to restrict commercial use. Are you okay with any company ignoring your license because you’ve posted it in the open?
The term source-available is exactly what you should be using instead of open-source, as the latter has been defined differently for decades.
The only instances I’ve seen people using the term open-source literally has been companies who wanted to benefit from positive connotations of open-source, while using a commercial source-available license which restricts many freedoms.
Another comment: https://linkage.ds8.zone/comment/1105950
If you want a share of their profit, how much is enough? Would it be a pay-what-you-want model, without any restrictions or how’d you define the minimum amount to stop them from donating 1$? A rate based on profits would be pretty much the same as charging a license fee based on a companies worth.
I get why you want to force donations, but at the same time restrictions like that aren’t compatible with the FOSS freedoms. Like others said, dual-licensing or a source-available license is probably the closest you’ll get. It’s not a license I prefer, but it’s okay. For example I’d rather have a non-compete clause for two years than something being proprietary for eternity.
As I understand it, there isn’t really a canonical way to burn an ISO. Any tool that copies a file bit for bit to another file should be able to copy a disk image to a disk. Even shell built-ins should do the job. E.g. cat my.iso > /dev/myusbstick
reads the file and puts it on the stick (which is also a file). Cat reads a file byte for byte (test by cat’ing any binary) and redirects the output to another file, which can be a device file like a usb stick.
There’s no practical difference between those tools, besides how fast they are. E.g. dd without the block size set to >=1K is pretty slow [1], but I guess most tools select large enough I/O sizes to be nearly identical (e.g. cp).
[1] https://superuser.com/questions/234199/good-block-size-for-disk-cloning-with-diskdump-dd#234204
The I/O size is a reason why it’s better to use cp than dd to copy an ISO to a USB stick. cp automatically selects an I/O size which should yield good performance, while dd’s default is extremely small and it’s necessary to specify a sane value manually (e.g. bs=1M).
With “everything” being a file on Linux, dd isn’t really special for simply cloning a disk. The habit of using dd is still quite strong for me.
This will help eliminate excess baggage that builds up over time by automatically removing end-of-life runtimes that are no longer used. As the system is updated to use new drivers/run-times, the old ones can be automatically removed.
This might solve the issue with flatpak nvidia driver versions not being removed and accumulating over time. AMD/Intel don’t have this issue as a single flatpak mesa driver version can work with multiple system drivers. Nvidia’s closed source driver needs an exact version match to allow for flatpak’s sandboxed GUI apps to work.
At least that’s how I understand it, take it with a grain of salt.
Mojang/Microsoft actually releases obfuscation maps for Minecraft: Java since 2019. This maps the decompiled random class names to the official variable/class names used by Mojang devs.
In an effort to help make modding the game easier, we have decided to publish our game obfuscation maps with all future releases of the game, starting today. This means that anyone who is interested may deobfuscate the game and find their way around the code without needing to spend a few months figuring out what’s what. It is our hope that mod authors and mod framework authors use these files to augment their updating processes that they have today. These mappings will always be available, instantly and immediately as part of every newly released version. This does not, however, change the existing restrictions on what you may or may not do with our game code or assets. The links to the obfuscation mappings are included as part of the version manifest json, and may be automatically pulled for any given version.
https://www.minecraft.net/en-us/article/minecraft-snapshot-19w36a
As others have said, Java is pretty easy to decompile, so there were community maintained obfuscation maps before (huge amount of work).
Choice is one of the great things about Linux, and I don’t see alternative init going away. For most people systemd is good enough and solves problems, so I agree, in that case popular init diversity has gone away.
I feel like most of these “10 alternatives to xyz”-articles are basically a summary of alternativeto.net. Or they’ve just listed all projects they’ve found with a quick search. I’m almost certain they didn’t install them most of the time.
This also applies to “comparison” sites, which usually are a list of Amazon affiliate links. At this point, I don’t trust websites with affiliate links anymore, as they’ve never actually tried the products. Sadly those spam sites make it difficult to find actually good reasearched tests.
Back to itsfoss, they write many articles, and some are good, but they still are blog spam.
If I’m cooking, I make enough for a few meals. It takes a similar amount of time and it can be stored for a while in the fridge.
Also I don’t think hello fresh is able to have lower prices than supermarkets, and it’s easy to find recipes online. I won’t be surprised if those services go bankrupt in a few years.
Edit: I can’t recommend SponsorBlock enough. Hearing the same sponsor message again and again is incredibly annoying.
Off topic: ff2mpv is awesome. It supports many video sites (I believe everything youtube-dl does) and opens the video on a page/link in an external mpv window.
This helped me mirror a video without downloading to read the embedded subtitles (why uploads a mirrored video with subtitles?). Also playback speed and all other advanced features mpv supports are really useful
Well, did you know I’m vegetarian and used to run Arch? If you could show me your fridge and computer, please, I’ll fix them for you!
There’s an increasing amount of wayland compositors, so I don’t think diversity goes away.
Additionally, hyprland supports plugins which can do most things an X.org window manager could do. E.g. there’s a plugin to support river’s window layout protocol, which allows for creating custom window layout generator.
Diversity doesn’t just vanish, it’s replaced by new possibilities, created by solid protocol specifications with multiple implementations.
Similarily, nixpkgs and other repos continue to grow, just like flathub does too. These projects aren’t killing diversity, they’re enabling it.
I personally prefer top level subvolumes (@, @home, @var-log, @var-cache), because it makes it easier to know which system folders are subvolumes and back them up accordingly. They are then mounted at their respective location under
/
.E.g… I do snapshots looking at the btrfs filesystem and its top level subvolumes. I’m not doing snapshots going from the mounted root filesystem. I.e. I’d do a snapshot of
@home
, not a snapshot of/home
.If you want to use backup/snapshot automation tooling, I’d recommend looking at how they expect the subvolumes to be set up. E.g. snapper and timeshift expect a specific layout (which can stil be done manually after OS installation, but why bother).