nize 🇵🇭

WE'RE SO BACK! Windows is so back. Today, Microsoft officially confirmed it's making Windows 11 a better operating system. This is a great news for consumers, competition, and of course Microsoft. In 2026, Microsoft will focus on its plans to "raise the bar on Windows 11 quality." It'll focus on performance, reliability and well-crafted experiences. These areas have meaningful impact on how you experience Windows: how fast it starts and responds, how stable it is under real workloads, and how consistent and thoughtful the experience feels - Microsoft "The team and I have spent a great deal of time analyzing your feedback. What came through was the voice of people who care deeply about Windows and want it to be better," said Windows boss Pavan Davuluri, who deeply cares about your feedback. Moreover, Microsoft is scaling back Copilot in Windows 11 after feedback to focus on: 1. Faster and more responsive Windows experiences, including reductions in apps like File Explorer 2. Improved memory efficiency, lowering the baseline memory footprint for Windows, freeing up more capacity for the apps you run. 3. More consistent performance, even under load, so apps stay responsive throughout the day.

Over time we kept running into the same problem with Prisma ORM. The architecture that got us here started slowing us down. Fixes took longer. Adding new capabilities got harder. So we asked: what would Prisma look like if we rebuilt it today?

if you don’t put in effort into curating the life you want every single day, you’d wake up one day and several years have passed.

Apple has 2 billion users now. 99.9% of them do not care about the icons.

We found that the fix to address the DoS vulnerability in React Server Components (CVE-2025-55184) was incomplete and does not prevent an attack in a specific case. This is disclosed as CVE-2025-67779. New patches are available now, please update immediately.

let's talk about unsafe rust. the biggest myth is that unsafe "turns off the borrow checker." that's just cap. all your normal, safe code inside an unsafe block is still 100% checked. unsafe is just you telling the compiler: "i'm enabling a few special stuff (like raw pointers) and i personally guarantee this code is correct." why? to build safe tools that the borrow checker is too dumbass to understand on its own. so, where do you actually see unsafe? FFI (talking to c/c++): this is the big one. every time you use a crate that wraps a c library (like openssl, ffmpeg, or just basic os calls), it's unsafe under the hood. rust can't check c code, so it's all on you. building safe stuff: your favorite types. vec has to use unsafe to get raw, uninitialized memory from the os. arc and mutex use unsafe to do the low-level atomic operations for thread safety. someone had to write this 'cursed' code once so we can all have nice things. peak performance: this is the "i'm smarter than the compiler" case. using get_unchecked(i) in a hot loop where you know the index is valid. or, using simd instructions (std::arch) to do parallel math on your cpu. high risk, high reward. low-level os/embedded dev: writing a kernel? talking directly to hardware? you're basically living in unsafe blocks. you have to write to specific memory addresses (0xb8000 for vga, anyone?). there's no 'safe' way to do that. you're not writing unsafe every day. you're using the safe tools that unsafe made possible.

Never do this: Passing off someone else’s work as your own. This Grok Imagine effect with the day-to-night transition was created by me — and I’m pretty sure that person knows it. To make things worse, their copy has more impressions than my original post. Not cool 👎