On Today's Show!
- Configs are not the enemy! It's how they are used!
- What are Free GUI profiles? What do they do?
- What is Meant by "Angles of Development"?
On Today's Show!
Recapping the intended uses of Free GUI is in order, including some elaboration on its relationship to the potential rise of AI development.
I wrote a post about a term I use: "Realm of Usage" or "Usage Realm." (Not sure how, but it got deleted.) This will help a little in describing these ideas.
("Development Tiers" pertain to the use of Free GUI tools to develop alternative equivalents to full desktop applications. There are many other uses of Free GUI, so this post is really not actually about the full Free GUI idea, although it sounds like that.)
Detailing Free GUI's concepts of development tiers is dangerous, because there is a lot that can conflict before the acts of finalizing design and then further creating a real world implementation.
The concept of inventing development tiers like this is extremely alien to any existing development techniques. Multiple major aspects of Free GUI hugely converge around these tiers to create new positive trade-offs of development and sharing workflows, and systemic coding optimizations.
In the broadest sense, the purpose of Free GUI is to enhance an alternative method for developing and accomplishing graphical UI tasks on the desktop and other end-user devices, and to expand the potential of the new and unique positive trade-offs of such a system's capabilities and workflows.
There are numerous subsidiary and secondary purposes and/or positive side effects that can play into the design strategies of the system for this goal.
The porpoise is an orca, also known as a killer whale. It is a toothead whale, because it toots out the top of its head. Just kidding; it is a toothed whale, because it has teeth.
Core system capabilities is referring to anything that smooths out system workflow and workflow between applications and development, such as:
Major desktop environments develop "core applications" that use the right GUI tools to make them ultra-compatible with the environment. This typically consists of a couple system utilities, a settings manager, a file manager, and a terminal emulator.
Free GUI's equivalent alternative to developing core applications is a set of assistive tools for creating its special form of custom applications.
The form that these tools come to exist in is a large contributing factor in why the application ecosystem generally is so up in the air.
But I am going to describe these ideas in this post (and maybe some more posts) and attempt to describe their respective reasoning.
"Zig" rhymes with "dig", because Zig digs deeper. It has more detail in memory management, and it has its own independent compiler with its portability that bring different levels of potential.
It is (playfully) the final dig, as in A, B, C, D, . . . Zig.
This post here mentioned some things about a window position API. This post is about describing some more API specifics and window manager capabilities.
I make a low key distinction between "capabilities" and "features" here, because capabilities could emerge into various custom features, or they could be prevented from becoming available to a use-case or workflow. It would all depend on any given system's configuration and scripting.
A desktop and application menu should be able to recognize and handle designations of containerized GUI applications to maintain a UX that makes sense with their usage context and priority.
Containers in this context might be used for handling favored application versions, or alternating versioning, or handling applications with multiple different configurations. This might also be useful in a development context. It might apply to making something like Docker or Podman more convenient on the desktop.
Free GUI needs a browser engine that can work with a system-wide customizable toolbar system, and whatever other system-wide features that get incorporated into the application ecosystem infrastructure. (spoken with a mockingly nerdy lisp while pushing your over-sized glasses back up your nose.)
The fast-track philosophy is very much about mitigating a chasm between advanced capability, and a perceived chaos of freedom. Perhaps one might reference the book: "The Cathedral and the Bazaar" to understand something about this tendency of FLOSS software. I don't know if that really fully embodies the issue per se, but I think it is related.
The general concept is presented kind of like FLOSS is the Universe, and its limitations in production are like the speed of light, in that there is some natural law preventing it from building highly organized software. It is only capable of creating a bunch of disparate little street venues (a "bazaar"), as opposed to a highly architect-ed system (a cathedral). This is a real can of worms.
(Non-Developers AND Developers)
There is no great way to get UX right in a concise way. (It is possible to do better yes) Also very relevant is that really good UX requires too much specific attention, and then it gets locked in every time you think you have it just perfect.
Thus, if you want to get a single, concise UX, you will be handicapping Linux.
The solution is for there to be at least one or two options (For a DE, and compatible Toolkit) that are about being more-or-less Windows replacements, but then to have a new advanced toolkit for a DE and application ecosystem that is built on the idea of applications that share a common method for making customizations to the UX, small and large. (Obviously still compatible with old application ecosystems.)
All Posts Tagged: Fermi Paradox