Arthur Wallendorff

A unique raccoon was spotted in Seattle A raccoon named Jimothy with a rare short spine syndrome was roaming the streets, stealing food from trash cans and frightening locals with his unusual appearance. At first, residents were startled by the strange-looking animal, but he later became a local celebrity, with people even making memes and drawings of him.

I'm sick of every single cold email with "AI solutions", I'm not just "marking them as spam", I'm starting to answer without any kind of patience or empathy to that.

Accidentally the most dramatic camera work ever seen in the commons just now...

Requiring your email address and full name to pair with and setup a dashcam is insane

FreeBSD just removed every single line of GPL code from its base system. The last piece was a small terminal utility called dialog. It is now replaced with a BSD-licensed equivalent. Sounds like a minor stuff? Not exactly. This completes a years-long effort to make FreeBSD's entire foundation free of 'copyleft obligations'. Why does this matter if you're not a BSD person? Because it changes what companies can do with the OS. GPL code requires you to share your modifications. BSD code doesn't. That's why FreeBSD (and its relatives like macOS's networking stack and PlayStation's OS) has always been attractive to corporations who want to build on an OS without releasing their changes back. With FreeBSD 16, that freedom extends to the entire base system without exceptions. The Linux world operates on a different philosophy. GPL is a feature here, not a bug. GPL ensures that improvements come back to the community. Watching FreeBSD cross this finish line is a reminder that the open-source world runs on more than one idea of what "free" means.

Thank you! Here are some thoughts I have (would be a bit longer): I previously looked into Odin, Jai, and Zig, but I eventually realized they may not be viable for me. The main reason is that if a language still requires manual memory management instead of using type theory, it's essentially the same as having to remember to pair malloc with free. This is a major source of bugs in programming. We invented garbage collection, linear types, and more to avoid this. I honestly don't see the point in going back, especially since Rust has proven that type theory can achieve zero runtime overhead in systems and low-level programming. I don't care that much about compile times; as long as it's better than C++, I'm fine with it :D That said, I'm not convinced Rust's approach is perfect either. It still caters too much to manual human programming. Rust uses affine types rather than strict linear types. This means you can either explicitly drop a value or let it be dropped implicitly when it goes out of scope. However, this implicit behavior can lead to unexpected issues, such as many "when local variable dropped" issues, and implementation difficulties when drop and async drop coexist. In the current era of AI-assisted or AI-driven programming, I don't think it's a problem to require every drop point to be written manually. It isn't even that complex for a human to write, let alone an AI, and it makes the entire code much clearer. Going back to languages like Odin, the fundamental issue remains: if you still have to worry about who owns what and who is responsible for calling free, you can almost guarantee you will write bugs.