Yeah, I’ve filled 256GB pretty easily by recording on an action camera all day, maybe for a couple of days. 4TB would be very convenient for a holiday.

Yeah and this still wouldn’t cover something like xz-utils because I would only be aware of end user projects and not the libraries behind them. I’d have to draw up entire dependency graphs.

Now run an emulator within an emulator for extra acceleration.

Good to know the name, I’ve seen it invoked a few times.

In fact, I had this recently at work where I questioned a decision only for them to retort with one similar characteristic which a prior suggestion of mine shared. This was also a modal fallacy as they only used that one characteristic to come to a conclusion about both.

You also see it all of the time in politics unfortunately, a lot of “yeah but you also…” where we should be hearing good justifications.

I was going to say that Cloudflare uses nginx but I found that’s no longer true.

deleted by creator

DMCA takedown from Meta incoming

To be honest, I agree they should be able to be larger at times.

I had a lot of disagreements when I was on a new codebase, knew what I was doing and I was able to push a lot of code out each day.

The idea is to have them small, easily readable with a tight feedback loop. I argued that bootstrapping a project will have a lot of new code at once to lay the foundations and my communication with the team was enough feedback. If I split it up, each PR would have been an incomplete idea and would have garnered a bunch of unnecessary questions.

That said, I think it’s generally pretty easy to put out multiple PRs in a day, keeping them small and specific. As you say, half of the job is reading code and it’s nicer to give my coworkers a set of PRs broken down into bite sized pieces.

I’d be pulled up at my job for any PR exceeding a few hundred lines. I don’t even know what they’d do if I just dropped a 15000 line stinker.

Have you seen the Star64?

Yeah, I think that comes from the developer having high standards for hardware security. The effort put in is a waste if the hardware fails. I would have thought Samsung would have been suitable too, though.

What about /e/OS or plain old degoogled Lineage? I like it as a phone OS, it’s just a shame the app ecosystem is so dependent on Google’s services.

I need to get into NixOS but I have a similar variation on servers: ansible for state of systems, Borg + Borgbase for data (kept in /srv) and code (including ansible) are in Git.

The separation between data and state is really great. You want to be able to go from a base install and only bring in everything which makes your setup different.

Easy come, easy go, will you let me go?

I don’t even mind the shortened arguments too much, though it doesn’t help. It’s more that every example seems to smush them together into a string of letters.

I would have found

tar -x -f pics.tar ./pics

to be clearer when I was learning. There’s plenty of commands which allow combining flags but every tar tutorial seems to do it from the beginning.

Sounds like someone has sticky fingers.

If we can travel faster than the trolley, we could adjust all switches with one person who continues to travel to the next junction before the trolley arrives!