Readers would understand what happened better given a distributed systems example. Lots of problems come up cold starting distributed systems that aren't explainable through "black start"
> Readers would understand what happened better given a distributed systems example.
Readers who know about distributed systems and their failure modes already understand the thing being explained. They (and you) are not the target audience. Let people who are not already experts learn something by analogy.
The mass hysteria around the "Epstein files" is largely justified given how widespread abuse was, but many people are really trying to invoke guilt by association / guilt by proxy even when there is nothing particularly revolting about specific individuals mentioned in those files.
I would have thought HN would be more sensible in this discussion. Alas, newly-created throwaway accounts are already here trying to derail the discussion.
People who just have a superficial knowledge of what Epstein did are the quickest to jump on guilt by association.
You have to remember: Epstein was always looking to expand his network and reaching out to any person of interest he could find. The fact that someone replied to his overture in and of iteself doesn't mean anything. He was like a fisherman, always casting lines into the water to see what bites. Once he got to know you better, he'd judge your value to him and your propensity to do illegal/immoral stuff and then blackmail you if you went along.
We use this on some graphical Debian servers at work. I hate it. The servers are beefy and the displays have high resolitions. There is no technical reason for having to use IceWM. Our 63-year-old veteran colleague simply likes it and blocks suggestions to move to a modern minimal WM. There are better options in big 2026. I cannot wait until he retires, so that we can retire IceWM.
There are about 300 people working daily on these servers. I'm team "enlightenment" and got about 50 people supporting me. There is the i3/sway camp (30ish people), there is the dwm camp (10-15 people), and there is the "please anything with modern UX at all" (estimate: 200 people).
I remember at university, we'd all log into our remote X sessions at the start of a lesson. I used blackbox back then which zipped along quite happily, but 30 people all trying to boot up KDE 3 at once rarely went well. I'd say careful what you wish for, but I assume modern servers can handle this better.
The few Linux desktops (clients) we have already use modern Gnome (I like it). We're talking about specialized servers where the GUI is an afterthought because resources are dedicated to efficiently and securely performing tasks. That's why anything more modern but with small attack surface would actually suffice...
I always thought that it was Mrs. = missus, Ms. = miz, at least that’s how I would say them, but I now realize that a) that’s plainly incorrect and b) I’ve never actually ever seen them non-abbreviated.
If an abbreviation is never expanded, is it still an abbreviation? Personally I think it isn’t; I advocate for condensing i.e./e.g. to simply ie and eg, though this is a minority opinion.
Seems to work for many websites. But only if your users aren't giving you money, because it's 50/50 whether they'll use a different email address or give up entirely.
I agree. I mean, his conflict of interest is obvious, but what he was addressing there has been exaggerated. He made no egregious statement. From a utilitarian perspective the distribution of RAM for local inference purposes is indeed inefficient. I still don't want OpenAI or any other company to be able to hoard huge orders of RAM, but the point applies regardless of OpenAI or Anthropic (or any other company). The knee-jerk reaction from a community that's supposed to be bright was disappointing though.
While Win32 tends to deliver the most resource-efficient and responsive apps if the complexity is not high, I have settled on the latest .NET + C# + Windows App SDK / WinUI 3. Making an app look good and fit into the modern Windows look is extremely hard with Win32 C/C++ and writing and maintaining it requires energy that I'd rather spend elsewhere. Besides, modern frameworks are making great strides in speed, efficiency and QoL features. .NET 11 is full of optimizations, for example.
I've tried this and found the WinUI deployment model frustrating and user hostile. There are like 5 open issues on GitHub where people seem deeply confused (I'm one of them) as to if it's possible to build a plain .NET .exe. Some people have tried it and it "works", others try it and get obscure errors, it's a real mess.
It's definitely possible to build a self-contained EXE. It's not easy or the default for a number of reasons, including the fact that going back even to DOS the PC application deployment model for applications is folders full of shared library DLLs and a smaller EXE that makes use of them. (The Win32 page model was built on it.) Modern .NET excels in that, including in the classic DOS installer model of "just copy the files, no installer required (but you'll probably build one anyway for extra branding opportunities and a few bonuses)".
Some .NET versions <= 4 installed a lot of their DLLs globally in Windows and if you were exact version tolerant enough (and GAC binding magic lucky enough) you could distribute a single EXE without an installer and expect some number of Windows users it would "just work" with only the EXE (and other users you would get complex dances of Windows Updates and .NET Installers to debug). Modern .NET decided on the classic DOS style "folder of DLLs" model over "global DLL cache and DLL Hell". You can no longer assume that the output EXE can "just work" on some supported Windows machines, but can better assume that the output folder of DLLs and EXE will work as intended generally on every supported Windows machine.
Not everything is flowers and sunshine (got a couple of open issues myself... in .NET MAUI too), but whether one can build a single, compact, self-contained exe does not define the hostility of a framework or platform, IMO. .NET was conceived as an enterprise-friendly development framework and that's where it shines the most. Quick-and-dirty/mean-and-lean/distribute-and-forget development was never its forte. I would appreciate that feature too, but it's largely a non-issue.
Apart from deeper technical issues: I don't like how wxWidgets look and that touch is seemingly not considered a first-class citizen like mouse+keyboard (yet).
reply