copygirl

Something else to consider in place of or in addition to a build number could also be using the git commit hash of what you’re building. Though I would only use that for non-stable releases.

For example, stable versions of Zig look like 0.12.1 and then there’s in-development releases like 0.13.0-dev.351+64ef45eb0. It uses semantic versioning where the “pre-release” is dev.351, which includes an incrementing build number, and the “build metadata” is 64ef45eb0, the commit hash it was built from. The latter allows a user to quickly look up the exact commit easily and thus know exactly what they’re using.

Version 5 of a software, device, vehicle or such isn’t necessarily better than version 4, and no official definition of the word “version” require this, either. If I may make another anology: You may pick one of 5 different versions of an outfit to wear, and even though they were labeled in the order they were made, from 1 to 5, none are inherently, objectively better than any other. In the case of UUIDs there are versions that are meant to supercede others, but also simply alternatives for different use-cases. Anyone with access to some up-to-date information can learn what each version’s purpose is.

1. There is the --download-sections option. Looking at it, you might want to use --download-sections "*0:00-1:00".
2. I briefly checked with --list-thumbnails and it doesn’t look like YouTube offers any square ones, so I would look into using ImageMagick to edit the image with a command. I doubt yt-dlp allows you to do any sort of image manipulation out of the box.

I might be too old-school for this but this video felt like it focused on AI assisted programming and I really don’t give a damn.

And you can use the with expression to create clones of the object with some properties modified.

Zig hasn’t been mentioned yet, so I’m just going to drop that here.

I personally have enjoyed the meta-programming, the ease of integrating with C libraries, and like that it’s pretty straight-forward to compile.

There used to be this service called Flattr, and it’s still around, but I’m honestly not sure how it works anymore. The way it used to work is you set a monthly amount you’re willing to contribute, you get to specify which projects to support, either one time, or recurring, and then your contribution is split up between the projects you chose to support.

I don’t know if this is an ideal system, because some creators might end up staying unsupported even though people are using their creations, others end up reminding their audience constantly to use the service and support them, so they end up with more than a similar creator not reminding their audience.

In the end, I think the best thing for all creators would would be universal basic income. Everyone is taken care of such they can survive and pay for necessities, and then they can just create stuff for others to enjoy, for free. (Oh, the humanity!) No trying to convince people to share part of their hard-earned money just for basic survival.

Gitea was taken over by a for-profit company, Forgejo is a fork by the previous maintainers to continue it fully FOSS without any of the shenanigans. See also their FAQ.

If you go by what the loudest ones are saying about the headphone jack removal, then yes, it does give the appearance that it’s a very unpopular change. However if you were to just ask random people on the street if they use(d) their headphone jack and what they think of this change, you’ll probably find there’s not a lot of vocal people out there that would not buy a phone just because it was missing it. That’s why Fairphone did their market research, right? Of course it’s still up for debate whether that was the right choice. And personally I would also prefer if the headphone jack was still default on phones.

Also see their official response on the audio jack removal.

TL;DR:

• Modularity and its influence on the phone’s size and weight
• Market and legislative trends (headphone jack is getting less popular)
• Longevity (less ports = less vulnerable to dust, water and general wear?)

This works until you have debug .NET.

This is called A/B testing. They’re rolling the feature out only to some users to see if it has the effect they’re going for, before rolling it out to more, or all users. (Also to ensure there are no bugs introduced by the changes.)

The IRC protocol is defined by a couple of RFCs, the first one being RFC 1459.

Isn’t creating a community from scratch already massively discouraging? Who will engage in a small community with barely any content if there’s already a bigger one out there? One reason I could think of is there’s some reason why the bigger community is not worth being part of any longer, such as bad moderation. In this case, creating a new one seems like the solution.