‼️🚨 BREAKING: GitHub has been compromised by TeamPCP. GitHub has confirmed the internal breach. A poisoned VS Code extension on an employee device exfiltrated ~3,800 internal repositories.
TeamPCP is already selling the data on a cybercrime forum.
@SahilSatralkar@Arsenal I feel it too. After all that we've suffered with this club. Imagine walking into school after that 10-2 at Bayern. We've suffered so long I almost can't believe we did it finally
I love this club. 22 years we have waited. Enjoy it until your hearts are full. This fanbase is family to me. So so proud of Arteta and the squad. We have done it.
Champions of England.
I promise you this is only the start for this beautiful institution.
COYG 😭❤️
in some ways ios development still feels like one of the purest kinds of programming. you have access to extremely powerful out-of-the-box ui frameworks, whatever sensors you want, low level memory access and C-family language interop, neural engine...
Advanced Swift Concurrency: Atomics vs Actors vs Mutex
I wanted to find out whether the new iOS 18 Synchronisation primitive, Atomic, was any good compared to Actors and the new Mutex.
I put them head-to-head counting concurrently to 10 million to get a benchmark for the fastest approach. The winner was… surprising.
See the full comparison here: https://t.co/KftXLfw7Ra
People say AsyncSequence was the Combine killer, which is bullsh*t because I love Combine. Using Combine is a great way to signal to your team that you're smarter than them.
Both libraries deal with streams of values over time. Many of the algorithms in the AsyncAlgorithms package therefore serve as drop-in replacements for corresponding Combine operations.
If you can't beat 'em, join 'em. It’s pretty easy to seamlessly convert Combine publishers into Swift-Concurrency-friendly AsyncSequences using the values modifier.
See my full migration attempt here in "Migrating Combine to AsyncAlgorithms"
https://t.co/r20yAWHqO4
It's hard to keep working with this continuous macOS virtual memory bug causing kernel panics. If some Apple kernel developer is around, please look at this:
panic(cpu 11 caller 0xfffffe0054388010): cpt_mapcnt_inc: refcnt overflow: rc 0xfffffde002fabb38 old_value 2050 value 2052
Debugger message: panic
Memory ID: 0xff
OS release type: User
OS version: 25E253
Kernel version: Darwin Kernel Version 25.4.0: Thu Mar 19 19:26:07 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T6031