Why does it have to be a CEO? You can always send somebody lower down, who actually knows their stuff. Requiring it to be the CEO is just dumb status games.
The problem is that nobody really does that? Like, as far as I'm aware, even simple stuff such as not considering tokens that would result in a syntax error when writing code isn't being done.
Incredible how Adafruit-sided this discussion is, having seen ptorrone serially creating alt accounts fediverse to harrass people who thought that his behavior was bad [1], going as far as to harrass people on their Etsy stores [2]. I do not expect anything he says to be truthful at all, after having seen how much abuse he spews out.
That's not strictly correct, it's rather that the current encoder does no inter-frame compression. Patches (and the frame system in general) does give tools to do some inter-frame compression (not as many as in video, but still quite expressive), just nobody stepped up to implement compression using them for animations yet.
Don't ever mention PD 1.0, it's a cursed standard that was never actually used and that nobody should ever use. USB PD started with PD 2.0, and we shall never speak of the stillborn child that is 1.0
Sun is continuously running a very nice distillation cycle the size of the world that makes fairly clean water just fall out of the sky. It's only a question of where does it fall, and how much. If you want it even cleaner, wait a couple centuries for it to filter down underground, and get it from there - besides maybe a bit high mineral contents, that can easily be removed, it's essentially free, clean water. The only question is how much it's replenished in the area you're taking it from.
There's plenty of areas where there's more rainfall, than there is outflow/evaporation, with water continuously replenishing deep groundwater. "Saving water" in such areas is of little concern besides the basic, economic one of well maintenance - each one can only pull so much, and more usage means more wells, and more upkeep.
Youtube has been long normalizing videos standard feed, switching to a -14 LUFS target in 2019. But LUFS is a global target, and is meant to allow higher peaks and troughs over the whole video, and the normalization does happen on a global level - if you exceed it by 3dB, then the whole video gets it's volume lowered by 3dB, no matter if the part is quiet or not.
The stable volume thing is meant to essentially level out all of the peaks and troughs, and IIRC it's actually computed server-side, I think yt-dlp can download stable volume streams if asked to.
Companies that build themselves on selling open source software put themselves in the position where anyone else can copy them and compete with them on price, and price alone. This is clearly the disadvantage of open source. It brings plenty of advantages, which is why people do it - but you can't have only the advantages and no disadvantages of open source.
Open sourcing your product is a risky investment, and as with all risky investments, it might pay out, or it might not.
Hey, you now have a specific cost to point to when arguing for/against solutions that have this problem. "each deployment will cost us at least 12 specialist hours per year just replacing the certificates" is a non-negligible cost that even the least tech-minded people will understand, and it can be a good lever for requiring the support.
It's because S3 api is quite a fair bit worse than what they offer. They define their guarantees for storage products way more clearly than other clouds, and for blob storage, from my understanding, their model is better than S3.
It cannot route HDMI, partly because HDMI is built upon antiquated principles and doesn't really fit besides more modern protocol designs. USB4 would need to get entirely redesigned for tunneling native HDMI.
Having a DP to HDMI converter on one end though, that's easy.
Host-to-host connections over USB4 (which is Thunderbolt without Intel's marketing) actually just have a packet interface over which you can pass IP, no need for Ethernet emulation.
> Quite a disciplined policy by the stewards of the website. How does the enforcement work against say, overtagging?
Tags are used as negative signal, rather than positive (as in, you filter out tags you don't like, rather than taking the ones you do), so overtagging would kill the submission, and missing tags will be added by others via suggestions (which automatically add the tag after some threshold amount of suggestions).
From my experience it's a lot easier to learn another language than to learn a new model of operation or new concepts entirely. And if you'll want to work with Godot, that will likely be the main barrier, and the main thing that will not be transferable to other contexts. The language however, can only make working with the concepts easier or harder. Godot team has decided that having their own language designed for dealing with the concepts of the engine makes it easier to use and results in less work than trying to adapt some existing language to the concepts of the engine. I've dealt with this a couple times, where a language was transformed so much by the context it was used in, it felt like an entirely different language.
Considering how few people do so, I'm fairly certain it would take more than a month for somebody to catch that.
But I guess it's also fairly easy to test it: just serve a slightly different version to the google's go mirror (by the user agent), and see how long until somebody complains to you about it.
If the proxy changes a new version of a package, when you update it, there's no way to detect it since it fetches through the cache anyways, so a poisoned sum will be added to sumdb, and anyone who isn't fetching their packages through Google's proxy will get told that whatever they're using is trying to trick them.