ASIO was just one of the first audio APIs to provide high-quality, low-latency audio. Many people haven't realized that native audio APIs have moved on since then.
macOS has proper audio APIs out of the box, and arguably since the introduction of WASAPI exclusive mode and WaveRT in Windows Vista, Windows has all the needed tools as well. But most of the more "professional" DAW products (in particular those by Steinberg, the author of ASIO) seem to ignore the existence of those. REAPER is one of the exceptions. Even WASAPI shared mode latency is really usable (below 30ms), but not low enough for tightly synchronized real-time recording.
Linux audio can be set up to provide low-latency audio as well, but I cannot comment on the details there as I'm not using it for that purpose.
Your average networked game these days is probably a bazillion times more secure than one from 20 years ago. It was super common that there were cheat tools to crash all game clients in a match. It was super annoying, we can just be glad that it was usually not used for anything more nefarious.
On every. single. video. again. and. again. They don't remember your choice.
And it keeps the auto-translated video title, so if that one is garbage there is extra work involved in figuring out what the original title meant to say, too.
If the font contains the missing emojis, sure. Emoji fonts tend to be huge though. The base Roboto font doesn't contain the emojis IIRC, there's a separate Roboto Emoji font for this reason (it's several dozen MBs).
It's absolutely infuriating. It could be such an awesome accessibility feature if it wasn't force-enabled by default. But what we get instead is YouTube engineers assuming that everyone just speaks a single language and needs auto-translations on every video. For every channel where this feature is enabled, I have to keep switching back to the original English audio track on every single video because YouTube knows that just because my primary browser language is set to German (the secondary language being English, btw), I am incapable of understanding the original audio track, of course.
This affects all digital stores. Many labels appear to have lost their uncompressed masters, especially for stuff that was released on the internet in the early 2000s. I regularly catch them pants down when trying to buy something through digital music stores as lossless and I receive a FLAC file that shows clear signs of MP3 compression. It usually results in a refund from the store in question. For this reason I'm buying less and less through those stores, and try to hunt down cheap used CD copies instead, if at all possible.
Stuff like this is why I keep printing entrance tickets and the like. I don't want to end up in a situation where I have to trust software that is known to have new bugs every months to get into a place without any sort of backup.
Well, Visual Basic .net is based on the .net framework, can't deny that. It's a very different language from the previous non-.net Visual Basic versions, so much that some people rather argue that "Visual Basic" is the problematic part of the name, not the ".net".
> It cost at the very least the salary of a software engineer, though most likely a lot more. Autodesk is not some passion project of a group of volunteers who just want to keep it up.
It's not a passion project, and that's why I find it very unlikely that they are not using some off-the-shelf forum software. I doubt Autodesk would be paying anything near a full software engineer salary for anyone working on the forum. Of course there will be some developer integrating the forum with the rest of their website, but that is hardly a full-time job. Moderation is probably also not done by engineers but by support staff that doesn't receive a salary at the level of an engineer.
In this particular case it's my use of NiMH batteries, which have a different discharge slope than normal Alkaline batteries. So it's not really a "feature" of the device but rather a limitation of the type of batteries used. With my alarm clock the signs when to charge the batteries are very obvious (the LCD starts fading away so it becomes hard to read, but the device is still functioning perfectly for some more weeks even then - it just doesn't much power at all).
It comes with other benefits as well. Not even the cheapest alarm clock has ever failed me. Sure, it can run out of battery power but the low power icon shows up months before it runs out of juice. Phone alarms on the other hand? I had them not triggering at all, or the vibration motor in the phone being stuck (?) and thus not working temporarily, etc... Hence I also prefer physical alarm clocks without software that have one job and one job only.
The intent is clear, yes. But given how well-known this problem is by now, I would expect a company of the size of Google to have a practical solution to combat this sort of scam, e.g. requiring that the vanity URL points to page containing a specific advertiser ID in the HTML source, or that the canonical URL of the URL with tracking parameters points to the vanity URL, etc...
There's so many solutions to this problem that allow vanity URLs to continue to work. Google just doesn't care.
I think this came up before in the context of scammy Google ads. Apparently you can set any vanity URL you like to be displayed, which indeed seems like the perfect invitation for scammers if it works without any restrictions.
It reads like the intention was that turning the parameter (0/1) command into an integer parameter, where the previous value enabled = 1 should behave reasonably close to the old behaviour. 1 deciseconds is arguably close enough to instant. If the parameter were measured in seconds, the command would always have to wait a whole second before executing, with no room for smaller delays.
Depends on what you are hosting. I found that source code repository viewers in particular (OP mentions Gitea, but I have seen it with others as well) are really troublesome: Each and every commit that exists in your repository can potentially cause dozens if not hundres of new unique pages to exist (diff against previous version, diff against current version, show file history, show file blame, etc...).
Plus many repo viewers of them take this information directly from the source repository without much caching involved, as it seems.
This is different from typical blogging or forum software, which is often designed to be able to handle really huge websites and thus have strong caching support. So far, nobody expected source code viewers to be so popular that performance could be an issue, but with AI scrapers this is quickly changing.
What you are probably thinking of is "race to idle". A CPU should process everything it can, as quickly it can (using all the power), and then go to an idle state, instead of processing everything slowly (potentially consuming less energy at that time) but take more time.
Doesn't work for me. Just like stereograms. I just don't know how to "tell" my eyes to cross. Maybe similar to how I didn't figure out until I was 20-something how finger snipping works. Maybe by the time I'm 50 I can cross my eyes...!
It doesn't look like that polling code was used under Linux. The fix was to only poll on Windows XP, since apparently this wasn't even needed on newer Windows versions. The bug was also fixed in 2018, so you would only be affected if your distriubtion ships a severely outdated Qt5 version.
Only if you have manually associated them with your Github account so that they show up as "your" commits, as far as I'm aware (although I'm not sure how deep Github's integration with desktop tools reaches these days)
They appear to be SO excited about their new feature that they sent an email about it to every single email address associated with my Github accounts. Which is quite a few addresses that have been used for git commits over the years.
IRC is pretty much the opposite of the definition of a walled garden. Its content is not discoverable by search engines by default, but that is not the definition of a walled garden, which is typically a synonym for closed platforms where you have no choice how to access their content (e.g. being forced to use a specific client software).