Earlier quoted context omitted.
It pretty much embodies everything I hate in modern OSes. I know what I want to do and I know how I want to do it, get out of my way. Meanwhile modern OSes can't even handle simple "maybe don't steal fucking focus from window I am currently writing something in just because some other app decided to make another windows."
Totally agree. I'm sick and tired of apps "helping me," constantly interrupting with tips, "did you know .." rearranging my windows and so on. I want to get stuff done not start a journey and relationship with new code. And nobody knows better than the user what stuff they wanna do.
Mercury OS
71–80 of 165 posts
Re: Mercury OS
#72I see where they are trying to go with the "humane" approach, but the examples seem to require big companies to play along. For example, the shopping examples put the control back with the user, and companies supply basic info like pictures, pricing, descriptions. In real life, of course, they won't cede that control easily. You'll get the same sort of mess you see on Facebook Marketplace, for example..."for sale" li…
The web lost track after the dotcom. In the beginning there were protocols. Now we're in the corporate moat period, where N corporations build the same thing N times because each one of them wants to dominate the others. Consequently, we were left with low-level protocols and languages (http, html, css, etc); there is no standard for buying shit online, despite most businesses being online. No standard for payments, no standard for query/search/browsing, etc. Compare that with, e.g., computer graphics, where graphics vendors (except Apple) collaborate on the development of standards like OpenGL, Vulkan, OpenXR, and shit works relatively seamlessly modulo vendor bugs and extensions.
Re: Mercury OS
#73Re: Mercury OS
#74this design miggt be fit for narrowed down use cases for special set of users who can really appreciate it.
Re: Mercury OS
#75Re: Mercury OS
#76The Shell is the outer layer, the interface between the user and the system.
This should not be considered a solved problem, more research and experimentation is welcome.
In practice, systems should be designed for better Shell modularity, in many cases they can hardly be swapped.
Re: Mercury OS
#77This looks like the exact opposite of what I would do if I were to redesign operating systems. The job of operating system is just to run application and get out of the way, and most importantly be deterministic and reliable. I don't need my OS to "predict what I might need", I know what I need myself.
It pretty much embodies everything I hate in modern OSes. I know what I want to do and I know how I want to do it, get out of my way. Meanwhile modern OSes can't even handle simple "maybe don't steal fucking focus from window I am currently writing something in just because some other app decided to make another windows."
That said, I like the concept of this OS design. It reminds me a little of the theoretical concept behind Star Trek’s LCARS interface, where the interface adapts to the user and the task at hand. As a power user I doubt I’d use this myself, unless it could be installed on top of NixOS, but it might be more intuitive and accessible to a more general user base.
It will be hard to get rid of files and folders though, even for general users. As messy as that can get, it’s a simple abstraction burned into just about every human’s brain at this point.
Re: Mercury OS
#78Inhumane is a strange word choice, to say the least. It’s neat to think about the possibilities of future UX, but to suggest the current system is cruel just sounds ridiculous.
Re: Mercury OS
#79This looks like the exact opposite of what I would do if I were to redesign operating systems. The job of operating system is just to run application and get out of the way, and most importantly be deterministic and reliable. I don't need my OS to "predict what I might need", I know what I need myself.
Cf: The Anti-Mac Interface, for a bit of a tonic