Apple can't perform well with audio on Apple Silicon, either. In 2025 macos is the only OS with audio cracking appearing with CPU load. Even Linux is better

Yeah, this is a regression since macOS Tahoe. Amazing that it still exists after several patch releases, is audio working not a basic test case for Apple?

I’ve found it to be worst when using Xcode / simulator and having headphones on for music.

sudo killall coreaudiod seems to fix it for a while.

It's ludicrous. I remember when Apple took pride in the audio never stopping. Once a very long time ago my entire Mac froze, even the Force Touch trackpad was unresponsive, but the music kept playing. Now, press Volume Up and the audio stutters. Or AirPods randomly get choppy and then stop playing until you reconnect them. The heck?

To add insult to injury, I recently connected my headphones to my Windows gaming PC.

Sounded absolutely amazing, no skipping or crackling no matter what I was doing on the PC, nor how heavy I was cranking it. Quality was better than on macOS as well.,

My M1 sounded like an AM radio when driving the same headphones using the same software (Spotify lossless).

> sudo killall coreaudiod seems to fix it for a while

For me this fixes it for about 30 minutes then I have to do it again… and again… and again…

I wonder why some folks need to do it more than others

I've had it since the first macOS that shipped with my M1 Pro MacBook!

I don't think it's CPU-based, but I've always had an issue with my AirPods Max on my iPhone with audio cracking (my AirPods Pro work fine, and the Max works fine with my Mac)

I only have it when iphone simulator is running and using the same audio output.

Personally not experienced this. However, continuity camera seems to have gotten more unstable over the past months for me.

That drives me nuts. It happens more in my AirPod pros and gen 4 AirPods.

As merely a systems engineer sometimes having to create a Web app I really much appreciate the experience of building a well-separated app without layers of trivial but flaky boilerplate layers that is a REST API in a dynamic language. The Next app I built last year using heavily RSC is one of the most legible and easy-to-maintain apps I have created so far.

We'll see if the magic can be trusted on or if we need more explicit solutions to this, but the Next/RSC experience was vastly superior compared to writing another REST API that is never to be used with anything else than the accompanied React app, and I'd love to use it or something similar to it in the future.

The reason is probably that a REST API for a "BFF" is in many cases quite tightly coupled with the frontend, and trying to detach those in the system architecture does not separate them in some higher scheme of things. Even if the two parts could separated but would never end up used without another, the separation probably just makes an unnecessary barrier.

I mean the different aspects of my Next app are now clearly separated, but they do form functional units. The separation between frontend and BFF is gone, but that was a wrong boundary in small scale apps to begin with.

DDoS or just too many new legitimate clients?

Codeberg has been under DDOS attacks for most of 2025, someone out there has it in for them and has been attacking relentlessly. The volunteer team has been very transparent posting about in social media and their blogs.

I think that even with someone having it out for them, the unfortunate reality of running a web service in 2025 is you have to be prepared to handle this and going down for hours at a time isn’t handling it.

I think it's best to take their statement at face value. I have no special insight into the organization.

Define legitimate clients. I'd guess that a good number of their "clients" are AI scrapers.

Well, Win NT is an actual operating system, and Win 98 and Classic macOS are just horribly overgrown home computer shells in an environment they should never have been exposed to.

These phones couldn’t do the thing in question even when 0 years old, due to a bug, and failure to fix that is the reason for getting blocked from the networks

I have become dumber without having contracted covid or other respiratory diseases (which could have been covid). 2020s have been the era of fascism, war and communities getting torn, which does not really help with stress levels and intellectual performance.

He is dead inside

I bet the worst part of him getting shot, for himself, would have been ruining the final photos with an open casket

Yes, with the difference that Google would have to be compromised in order to poison the go distributable containing fmt tool. With js, it’s enough to poison any single one of the 1400 dependencies of the linter

I forgot that even though fmt will never suffer from middle man attacks downloading the Go toolchain, the standard library already covers 100% of the uses cases someone cares about using Go for, and no one is using CGO.

I used to use CGO quite a lot in linux-embedded environment.

And we had huge dependency chains as well to non-standard library stuff, nowhere near as bad as an average nodejs project but still not free from the problem.

Use biome, it doesn't have any external dependencies. eslint should have been put to rest a long time ago.

Good advice. That was my conclusion as well after years of fighting with eslint.

someone else recommended this too, I'll give it a shot next time I'm in js land.

We added biome to our project, now we have eslint, prettier and biome in the project.

Seriously though it is nice, but migrating away from your existing tooling is painful and underappreciated.

Finnish rural boys rarely have other personality traits than their favourite car brand. It’s usually BMW or Volvo, and friendships must follow the shared brand following. Someone driving a Nissan Micra should starve to death, according to both camps.

Sounds like Windows and Linux users talking about Macs

or Linux and Macs users talking about Windows, or Macs and Windows users talking about Linux

Favourite tractor brand is usually more important, though. :D