Ironically, I think it's the younger ones the ones pushing for discord the most. Some projects opened a discord because it actually made it more attractive to young people.

The question is how to make an open source alternative more attractive.

source: https://analytics.usa.gov/

This is the result currently (last 7 days):

 Windows   35.5%
      11   18.5%
      10   16%
       7    0.8%
    2000    0.1%
     8.1  < 0.1%
       8  < 0.1%
 iOS       29.6%
 Android   15.9%
 Macintosh 12.3%
 Linux      5.2%
 Chrome OS  1.4%
 Other    < 0.1%

If we exclude Android and iOS (which make for 29.6 + 15.9 = 45.5%), then the contribution of each of the others would increase (by 100/45.5 = 2.19), leading to 11.388% (5.2 * 2.19).

Honestly, I'm more interested in reliability and mechanisms to prevent data loss...

Last I checked, the exFAT implementation that MS released to the public was missing some key features that made the Linux port less reliable, particularly for removable storage devices (making it not much better than old school FAT). Has that been fixed already?

In Germany I've seen some vegan restaurants replace some letter with "v" for vegan.

Like "vurst" instead of "wurst" (sausage) or "vleish" instead of "fleish" (meat).

What do you mean by "not require sudo privileges"?

Do you mean not require root permissions? that depends on what are you trying to do. You'll need to make changes in your system to allow normal users to have permissions for it, and in many cases that's not possible (or very safe).

If what you mean is that you don't want to need to type"sudo" every time, but still be able to have the commands run with root permissions, then there's multiple ways to do this:

• Add an alias such as alias command='sudo command'. If you don't want to type the password, you can change the sudores file so that your user doesn't need to enter a password when running sudo for that command (someone else in the comments already explained how to do that, using an entry with NOPASSWD: /usr/bin/command in the sudoers config).

• alternatively: set the SUID bit of the executable you want to run, so that every time the file is executed (by anyone) it will always execute as the user who owns the file (so if the owner is root, the file will always be executed as root)... this is not something I'd recommend though, since it can lead to security vulnerabilities.

I mean, isn't that what "get on or get left behind" means?

It does not necessarily mean you'll lose your job. Nor does "get on" mean you have to become a specialist on it.

The post picks specifically on things that didn't catch on (or that only catched on for a period of time but were eventually superseeded), but does not apply it to other successful technologies.

git commit -m "$(fortune | cowsay)"

ATP (and any molecule, really) is just a particular configuration of electrical particles that use electromagnetism to hold together some mass.

If it's easy to patch this out, I wonder if there will be manufacturers that will choose to do so for their official ROMs. It would be extra value for the brand, imho. A reason to choose, say, Samsung, over a Pixel phone, if Samsung were to patch this restriction out, for example. After all, they also have the Galaxy Store which is also offering apps that I doubt they'll want Google to regulate.

If the original footage is so bad that "nonsense that people assume is part of the actual show" "could plausibly be there", then the problem is not with the AI... it wouldn't be the first time I'm confused by the artifacts in a low quality video.

I agree that we shouldn't worry (at least for the moment), but I think the main reason is the lack of locks, both when it comes to hardware (no locked bootloader) and software (getting root access is trivial, so you can uninstall whatever components you might not like and with updates not being mandatory you can keep it under your control).

With SteamOS, you already have an ecosystem, which is Steam. There is (at least for now) a clear distinction between Hardware manufacturer and software provider.

Currently, the only officially sanctioned version of SteamOS is the one that is shipped with Steam Deck (even though that might change soon), which is hardware sold by Valve (ie, the same company making the software). Meanwhile, most people using Android don't use Pixel / Nexus devices and thus their hardware is not being sold by Google.

So I'd say this depends entirely on how do the new manufacturers wanna go about it when it comes to offering their own custom versions of SteamOS. At the moment this is ok because Valve has been acting as a "benevolent dictator" and they have essentially had a monopoly on SteamOS 3 devices until now. Once that monopoly breaks (and if Valve actually allows third parties to ship their own customizations) we'll have to see what kind of control will their partners want to assert over it.

Awesome!

I assume it's storing the images and assets in base64 format, so it might get quite big. I always wished there was a standard way to package a website in a single compressed file. Sort of like an epub / ODF kind of format that keeps the website layout. But this is the next best thing.

Real programmers use C-x butterfly

What'd be the result for IsEven(1)?

For the record, you mention "the limitations of the number of inodes in Unix-like systems", but this is not a limit in Unix, but a limit in filesystem formats (which also extends to Windows and other systems).

So it depends more on what the filesystem is rather than the OS. A FAT32 partition can only hold 65,535 files (2^16), but both ext4 and NTFS can have up to 4,294,967,295 (2^32). If using Btrfs then it jumps to 18,446,744,073,709,551,615 (2^64).

Yes... "metadata" is becoming an overused term. Not all data is metadata.

My first thought when I read the title was about those .nfo files used by Kodi/Jellyfin and other media centers to keep information relative to the media files.

As someone who hasn't touch base with Nix for a long time: what are "flakes"?

Much of the water you and me drink, used to be pee and fecal sludge.

I'd argue that the systemd trend actually is the one that's change-adverse.

I remember that before systemd there was a lot of innovation when it comes to init systems… the flexibility of the script-based inits made it so most distros had their own spin. And there was more diversity in components that now are part of systemd. I’d argue that ever since systemd became the de-facto standard, innovation in those areas has become niche. Distros are becoming more homogeneous and less open to changes in that sense. Some components are becoming more and more interdependent and it's becoming harder to ship, for example, Gnome, without systemd.

But then you are not getting rid of the complexity, you are just forcing programs to become more complex/inefficient.

I experienced this with the doom libretro core, which is meant to be portable and have minimal dependencies... so if I need it to automatically find DOOM.WAD/ doom.wad/Doom.WAD/etc in a directory I would either have to add a globbing library as dependency to handle this case and have it fetch [Dd][Oo][Oo][Mm].[Ww][Aa][Dd], manually check for each possible case, or list the entire directory (I hope you don't have a library of a million wads!) and compare each file (after upper/lower) just to find the one with the right name. And that could be a real pain for embedded devices with low I/O or if there's a remote storage layer behind.