A desktop made for one

Personal, “Audience-of-One” Software

• Many commenters resonate with the idea of tools built only for their creator: no configs, no logins, no multi-user concerns, no polish beyond what the author needs.
• People describe similar projects (custom WMs, shells, editors, web tools, image viewers, automation apps) that are idiosyncratic and would be intolerable to others but “fit like a glove” for their owner.
• Some liken this to “home‑cooked” or “extremely/hyper personal” software and to 1980s home computing and BASIC, where writing your own tools was normal.

Role of LLMs and the Assembly Desktop

• The article’s desktop, window manager, shell, and terminal are largely written in x86‑64 assembly via an LLM coding agent.
• Supporters see this as a proof that modern LLMs can deliver substantial systems from high‑level prompts, reducing “years of work” to weeks and enabling non‑specialists or busy professionals to get custom tools.
• Critics argue that compilers from higher‑level languages (e.g., Rust) would produce smaller, faster, and safer code with less development effort, and that using LLMs to generate large ASM projects is mainly a stunt.

Performance, Efficiency, and Practical Gains

• The author reports dramatically lower power use and instant-feeling UI; some find this inspiring and reminiscent of ultra‑fast 1980s machines.
• Others point out concrete inefficiencies in the generated assembly (string comparisons, state dispatch, overuse of 64‑bit registers) as evidence that the “efficiency” is more about minimal dependencies than truly optimal low‑level code.

Cost, Time, and Practicality

• With a flat‑rate LLM subscription, marginal cost is described as near zero; estimates suggest that equivalent human engineering time would be very expensive.
• Several commenters emphasize that time, not ability, is the main constraint; LLMs let them make tools in hours or days instead of weeks or months, often in short bursts around work and family.

Security and Reliability

• Some worry about everyone rolling their own tools: more bugs, less review, and potential vulnerabilities introduced by LLM‑generated boilerplate.
• Others argue that highly individualized, non‑networked tools are unattractive mass‑attack targets, though classes of vulnerabilities may still be exploitable across many similar, LLM‑generated apps.

Cultural Split and Future of Software

• One camp “just wants the thing to exist” and is thrilled to offload code writing to agents; another values understanding, craft, and long‑term maintainability, and sees this as “AI slop” undermining skills and hacker culture.
• There’s debate over whether this belongs on an engineering‑focused forum, and over how much LLM‑written text and code readers should trust.
• Many foresee a “Cambrian explosion” of personal software (and eventually media) as coding becomes more like specifying behavior to an agent than hand‑writing programs, with new importance for underlying libraries, protocols, and ops.