> But if you actually have made things complicated enough [...]
The only problem I see in this case is that complexity doesn't come all at once. By the time you reach a problem that k8s is good at solving, you've probably already accidentally made a k8s alongside your piece of software.
In my(quite short) SWE career, I've seen software evolve, even ones with a proper design stage. Maybe I just don't have enough experience to have seen a properly designed project, but I don't know what I don't know after all.
In their paper, point 5.2.5 talks about their sandboxing platform(DeepSeek Elastic Compute). It seems like they have 4 different execution methods: function calls, container, microVM and fullVM.
This is a pretty interesting thing they've built in my opinion, and not something I'd expect to be buried in the model paper like this. Does anyone have any details about it? Google doesn't seem to find anything of note, and I'd love to dive a bit deeper into DSec.
I agree. Ever since the release of R1, it's like every single American AI company has realized that they actually do not want to show CoT, and then separately that they cannot actually run CoT models profitably. Ever since then, we've seen everyone implement a very bad dynamic-reasoning system that makes you feel like an ass for even daring to ask the model for more than 12 tokens of thought.
It should be noted that the CIX P1(this board's SoC) has ongoing efforts to be upstreamed. Last I checked, the GPU drivers were still not available(due to them not supporting ACPI? I may be wrong on this) and power draw being weird and stuck at 10-15ish watts. It seems like this blog confirms nothing has changed on those 2 points.
With that being said, CIX and their main board partner, Radxa, have been open with the UEFI.
I am not an expert in low-level environments such as the kernel or the UEFI, but if these tidbits sound interesting I would encourage anyone who is to look further into the CIX P1. To my untrained eyes, CIX looks like a company that is working towards a desktop/laptop chip with real UEFI/ACPI support. I look forward to the day it is polished up a bit.
Despite being a game framework, due to LuaJIT's great FFI you can just write whatever.
I recently made a tool that captures frames from GTA:SA using GDI, and when holding ESC only show gameplay frames. It's an anti-epilepsy 'filter' for pause buffering intended for streaming. Now I just need to start streaming SA speedruns.
What community is there to house around Microsoft Copilot?
Seriously, why does Microsoft Copilot need a Discord Server?
What do I talk about when I join the Microsoft Copilot server?
What are we doing here?
I believe Windows 7 also had a great user interface.
This talk from PDC2008 resonated with me, specifically the concept of "Delights" from 23:45 onward.
The truth is that even with KeePassXC, I just really do not notice stale passwords across devices.
It's just really not a huge deal for me personally. Maybe it is for normal people.
I sync my databases maybe once a year if I'm lucky.
It doesn't sound strange, it actually sounds sane and what everyone should be doing.
At the same time, I can't imagine the last time I had a random exception I didn't think about in prod, but I guess that's the whole point of the BEAM, just don't think about it at all.
I might take a stab at Elixir, the concepts seem interesting and the syntax looks to be up my alley.
> The BEAM's "let it crash" philosophy takes the opposite approach. Instead of anticipating every failure mode, you write the happy path and let processes crash. The supervisor detects the crash and restarts the process in a clean state. The rest of the system continues unaffected.
Do I want this? If my request fails because the tool doesn't have a DB connection, I want the model to receive information about that error. If the LLM API returns an error because the conversation is too long, I want to run compacting or other context engineering strategies, I don't want to restart the process just to run into the same thing again. Am I misunderstanding Elixir's advantage here?
The thing with Linux cheats is that they were significantly easier to make(you didn't have to think about bypassing the anticheat at all, you could just read the game's memory or LD_PRELOAD your cheat in), and a lot more were publicly available(in true FOSS fashion, a lot of Linux cheats were open-source). A cheat that could cost $30-$60 a month on Windows could be free as in freedom(and free beer) on Linux.
I am not a kernel developer, so I don't really have any idea what this means, but CIX appears to have patches in the Linux kernel[0], so I assume mainlining more stuff is in the works?
I believe Valve's concerns went(or maybe go?) beyond just the Windows Store, and into "We believe Microsoft may become unable to ship a good Operating System in the future".
In a 2013 interview with Gabe Newell: "Windows 8 was like this giant sadness. It just hurts everybody in the PC business. Rather than everybody being all excited to go buy a new PC, buying new software to run on it, we’ve had a 20+ percent decline in PC sales — it’s like 'holy cow that’s not what the new generation of the operating system is supposed to do.' There’s supposed to be a 40 percent uptake, not a 20 percent decline, so that’s what really scares me. When I started using it I was like 'oh my god...' I find [Windows 8] unusable." [0]
The Windows Store probably was a part of it, sure, but looking at that quote from 2025, after having your SSD broken, your recovery unusable and your explorer laggy? It's quite bitter-sweet.
99* and 00* are what I do during hackathons, not work. I write some of the worst, god-awful code I've ever seen during hackathons, because I need to get the idea working. I(and the company) can't afford to merely "get the idea working" in production.
I assume it will get reposted at some point.