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.

Technically, even an optical port can deliver power. Light is just a particular form of electromagnetic wave that just happens to use another method of transmission (and you might need a different mechanism to transform its energy), but it also has an intensity, potential energy and resistance in the medium of propagation.

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

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

It might have been horse-drawn in the 1890s with color paint, and years later photographed with a modern camera.

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.

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?

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

Allow blob:// videos to be saved normally. It’s just a file. I’m looking at it. Move it from memory to the hard drive.

True. Although in many cases this is indicative of a stream (not really a traditional file for the browser), but at the very least, even in the (rare?) cases that there isn’t cached content already, it should theoretically be possible to start saving the video the moment you press on the save button…

Already the “picture-in-picture” mode Firefox offers is a step in the right direction, imho. It allows the browser to take over control of the playback, which is something some places try to forbid.

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

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.

Real programmers use C-x butterfly

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.

I’m with you, and not just from a “human” perspective. Also when writing small programs meant to be relatively lean/simple it can be a problem when the user expects it to find a particular file regardless of its case (will it be DOOM.WAD or doom.wad? Doom.wad? Doom.WAD? … guess it’ll have to be [Dd][Oo][Oo][Mm].[Ww][Aa][Dd] and import some globbing library as extra dependency… that, or list the whole directory regardless its size and lower/upper every single filename until you find a matching one…)

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.

And if looking for Rust alternatives, there’s dua.

Particularly user friendly when called in interactive mode with dua i, you can navigate the tree immediately as it populates and calculates space progressively.