Windows by default? Omarchy asks a better question.
The default workstation deserves a reason. Omarchy shows what an open Linux desktop can look like, and how to assess whether a migration makes sense.
Read the German original
The default needs a reason again
Which operating system goes on a new work computer? That question deserves the same care as choosing your business software. Which applications does the person need, where is the data and who looks after the device? Our view for 2026 is that Windows should be assessed against these requirements. An open Linux workstation deserves serious consideration. Omarchy shows how appealing that option can look and feel.
The facts remain straightforward: regular support for Windows 10, version 22H2, ended on 14 October 2025. Registered devices can receive further security updates through the ESU programme; LTSB and LTSC editions have their own lifecycles. Windows 11 continues to be offered and supported. When we discuss the end of Windows as the default, we are proposing a business perspective, not reporting that Windows has been discontinued.
What DHH makes visible about Linux
David Heinemeier Hansson, known as DHH, introduced Omarchy in June 2025 as his preconfigured combination of Arch Linux and the Hyprland window manager. The idea is a coherent starting point that people can begin working with immediately and then change themselves. At launch, he already wrote that this approach would not suit everyone and that Ubuntu could offer an easier introduction. That is a clear product limitation.
In his subsequent Linux essay, DHH describes a sense of possibility among developers. He also warns against confusing enthusiasm in one's own circle with widespread adoption. We value that distinction. DHH is on X as @dhh; his detailed arguments appear in the linked blog posts. For us, the useful prompt is to make conscious choices about the workplace again and question its tools instead of treating them as inevitable.
The benefit appears between tasks
Omarchy combines coordinated design with a desktop that can be operated extensively through the keyboard and prepared development tools. Windows, the terminal and applications form a recognisable whole. This can help when moving between code, documentation and a running application. Real tasks provide a much more reliable way to assess whether the interaction works better for your team than a screenshot, however attractive it looks.
For example, a pilot might involve an employee handling customer enquiries in a browser, checking documents and working in an internal portal. We would test precisely those activities on the intended computer, including video conferencing, printing and file exchange. We would then assess learning time, smooth operation and support effort. An interface becomes economically useful through a working daily routine. Open configurations can also help document proven settings and apply them to additional devices.
Freedom needs a plan for operation
Omarchy's Arch foundation follows a rolling release model. Arch documentation recommends regular full updates; partial package upgrades are unsupported. For business use, we take this to mean testing changes on a pilot device first, recording a known starting state and practising recovery. Indefinitely postponing updates only defers the work. A system snapshot also does not replace a backup of work data.
Before migration, check business applications, document templates, required hardware and existing access methods. Omarchy documents a Windows VM for Windows applications that are still needed. This setup does not include GPU passthrough; licensing and suitability must fit the use case. A VM therefore does not automatically resolve every dependency. Employees also need a clear introduction and accessible support. If the requirements point to another Linux distribution or a Windows workstation, the pilot must allow that outcome without treating it as a failure.
Agents make the workplace adaptable
The current Omarchy manual treats SI agents as part of the work environment. It describes choosing a default agent, assistance with investigating crashes and customisation using supplied instructions, among other things. We see an interesting next step here: employees describe the behaviour they want, and technical support turns that into a change that can be checked. The workplace can gradually adapt to specific tasks.
For customer projects, we connect this possibility with clear responsibilities. An agent needs appropriate access, a bounded task and verifiable results. Changes to important system settings must be documented clearly and reversible. Choosing an external SI service remains a separate decision about data processing and cost. An open operating system does not automatically make connected services open source. The benefit lies in adaptable workflows and conscious decisions about the tools being used.
How this becomes neurofunken Workplace
With neurofunken Workplace, we offer planning and setup of Linux and Omarchy workstations tailored to employees' tasks. We begin with a work profile and a suitable pilot device. Together, we check applications, access, data exchange and everyday operation. We then agree any further rollout, training, updates and desired support. Scope, responsibilities and support are defined explicitly.
Our software approach supports this: browser-based applications, understandable interfaces and open components wherever practical make it easier to choose a workstation. This can prevent unnecessary dependence on a single vendor. Windows can lose its automatic status as the default. Your company's tasks should set the standard. Omarchy gives us a compelling reason to reconsider that decision together.
What does this look like in your work?
We can turn the idea into a sensible next step with you.
Plan a Linux & Agentic Workplace together