Arcan is a powerful development framework for creating virtually anything between user interfaces for specialised embedded applications all the way to full-blown standalone desktop environments. Boot splash screen? no problem. SCADA HMI for your home? easy peasy. Xorg backend? got you covered. Wayland compositor? sure thing.
At its heart lies a robust and portable multimedia engine, with a well-tested and well-documented interface, programmable using Lua. At every step of the way, the underlying development emphasises security, performance and debugability guided by a principle of least surprise in terms of API design.
From the about page, same site as OP.
> the ‘elevator- pitch’ to the modern tweet-length attention spanned reader goes as follows:
> Arcan is a curious blend of a streaming multimedia processor, game engine and display server with a novel design that lends itself well for both complex and simple realtime interactive graphics projects alike, and goes well with anything from Sci-Fi UIs for some homegrown embedded project to full blown desktops. It is highly modular, low on dependencies, yet comes with all necessary batteries included.
"The perspective is to instead emphasise the extremes, that is to focus on the small “one task” kind of clients and on integration with bigger “embedded universes” like virtual machines and web browsers, and leave the middle to fester and rot."
Lots of interesting write-ups and comments. Check them out.
Edit, to clarify: The only way I know I can send an invite is to input the email address and an invite message into my settings page at that site. I'm not aware of another way to send it.
I completely respect the project owners desire to fly under the radar, but man it sure seems like more contributors would be a good thing to help us finally move past the monstrous x11/xorg legacy.
In my mind, the best possible way to go about replacing X is making something that suits the way computers work today and the way computers are trending. That's why I really like Wayland. The entire point is to optimize for the local experience and anything beyond that is candy. It's designed for accelerated graphics first, which is what most client side users are going to have. It's even more important from a laptop perspective because of just how much more efficient the GPU is at rendering graphics.
As an aside, another great thing is that most the new features of linux and it's graphics stack that were created (at least in part) for Wayland are able to function completely outside of that environment. KMS, DRM, using full OpenGL or Vulkan without a display server, etc.
The lines between a "network terminal" and a "remote desktop" are essentially nonexistent.
Is this design a failure? How many Citrix, MS RDP, TeamViewer, VNC, etc. users are there for every X user? 100? 1000? More?
As others point out contemporary X isn't really network transparent. Extensions compromise network transparency for performance, among other reasons. This compromise is inherent to the requirements of popular desktop environments today. Is this not further evidence of failure of the design intent?
Why has X not to contributed to mobile platforms? X is a native citizen of at least one of the major portable OSes (Linux) and not too far removed from the other (Darwin.) Yet no X.
Cloud hosted gaming is upon us; Google, Microsoft, NVidia and others are building services. If X is the network transparent answer to rendering why is it not the basis for any of this?
Successful designs experience growth beyond their original niche. Yet after 35 years X remains only the display system for a vanishingly small fraction of the desktop computing world, and an alternative has emerged to displace it even from that.
I don't hate X. I use X heavily every day. But I don't have any illusions about its success or future.
Like, you can get "near" the concept - but definitely not there.
History is different, but practically they have been converging to a similar result.
You want to compare Arcan to a Wayland implementation. Like gnome-shell. Or weston.
Or Arcan. Adding Wayland support to Arcan has been a thing.
I understand Arcan is larger in scope than Wayland, but Arcan must have a protocol and architecture behind said protocol that can be meaningfully compared to Wayland's.
Part of the problem is that Xorg is much more well defined in that most can grok "what it is" so there is a point of reference to base an explanation from without 'too much' confusion, there's stuff to work on that isn't IRC logs or mailing list posts which is seriously 90% of Wayland right there.
Wayland is not a "protocol" in the traditional RFC/Jon Postel sense. Heck, even the spec PDF itself referred to itself as a Display Server. There's single X extensions with far more coherent descriptions than all of the Wayland Ecosystem. It's full of overloaded terms and technical WTFs!?. If anything, its the worst parts of Micosoft COM resurrected. An asynchronous Object Oriented IDL. Run for the hills.
Some say it'll fix security issues, it'll fix performance issues, it'll fix world peace -- with barely anyone answering or questioning "how", "why" or "why can't X?". When you counter-argue its feature anaemia it is "oh it's just a protocol, the compositor fixes that" and when you question the feature bulimia it is "oh that's compositor extensions, not the protocol".
Neither position is substantiated by its technical underpinnings, the protocol parts itself, nor the documentation, nor any of the the 'project goals'.
Durden : http://durden.arcan-fe.com is tiling, stacking, tabbed, and a few others rolled into one.
Prio : https://arcan-fe.com/2017/04/17/one-night-in-rio-vacation-ph... - much more simple one that builds on rio from plan9.
Safespaces : https://arcan-fe.com/2018/03/29/safespaces-an-open-source-vr... - 3D/VR.