René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add compile-time known design path","articleBody":"**Is your feature request related to a problem? Please describe.**\r\nCurrently, maxGUI works for systems that don't know their UI at compile-time and need to change things at run-time. This is good for situations where reading a file or fetching data from a server dictates how the UI should look.\r\n\r\nBut many apps do not need this flexibility. And they currently pay a bit of a price for it.\r\n\r\n**Describe the solution you'd like**\r\nThere should be a compile-time-known-design path (perhaps using type lists instead of type erasure, for example).\r\n\r\n**Describe alternatives you've considered**\r\nThe current path uses very little memory and performance overhead. It seems to beat many other GUI libraries already. So perhaps this optimization is not needed. However, it is still wasteful. (And as a side note: A programming pet peeve of mine is how much we know at compile-time but defer to run-time at great cost.)","author":{"url":"https://github.com/ProgramMax","@type":"Person","name":"ProgramMax"},"datePublished":"2023-07-04T08:25:26.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/74/maxGUI/issues/74"}