Ferk

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.

All you need is the promptbar. No need to waste resources rendering a bloated page. Have the AI summarize the contents in one sentence and then speak it out loud so I don't have to read.

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

Yes, but you know what I did? nothing, I just have the program exclusively accept lowercase doom.wad

This means it became annoying for the user. The problem shifted and now it's the end-user the one with the responsibility to read the manual and do the work. A lot of people just get a DOOM.WAD, put it there and are surprised it doesn't work.

And there are many many programs that are doing the same thing in many similar situations. In fact, in the Linux world, most software pushes this to the end user. So this is just as much of a problem for users as it is for programmers.

At the end of the day, the question should not be: is it more complexity for the user or for the programmer? ..the question should be: what's the end cause making it complex? is there a way it can be made simpler?

This is the same for every problem. Often user-friendliness is a tradeoff, most user-friendly software I've used keeps so much complexity within that it becomes annoyingly slow and inefficient. I'd rather use the terminal for file management than wait for the GUI file browser to finish loading my huge remote storage directories.

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...)

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.