Skip to content
TheChatArchiveThe Chat Archive
gpt-3.5-turbo-0613· OpenAIAi2 WildChat-4.8M (AI2)

To be honest, Lua is almost "perfect" (in some sense) embedded language (not for…

  1. User

    To be honest, Lua is almost "perfect" (in some sense) embedded language (not for embedded programming, I mean) for being small and expressive. What are alternatives? (do not mention Python - it is good, but it is too bloated to be really embedded in some sense)

  2. Assistant

    There are several alternatives to Lua that are considered small and expressive for embedded systems. Some of these alternatives include:

    1. JavaScript (specifically, the subset known as "embedded JavaScript" or eJS): It is a lightweight scripting language that is widely supported and has a smaller footprint compared to Python.

    2. Tcl (Tool Command Language): It is a scripting language known for its simplicity and small size. Tcl is often used for embedding in applications and has a C API that allows easy integration.

    3. Squirrel: It is a high-level imperative, object-oriented programming language designed for embedding in applications. Squirrel is lightweight and provides a simple syntax similar to Lua.

    4. Io: It is a small prototype-based programming language that is highly embeddable. Io has a minimalistic design and offers powerful introspection capabilities.

    5. Scheme or Lisp dialects (such as TinyScheme or uLisp): These languages are renowned for their simplicity and small implementations, making them well-suited for embedding in constrained systems.

    It's worth noting that the definition of "embedded" may vary, so depending on your specific requirements, other languages like Forth or Erlang might also be worth exploring. Ultimately, the choice of an embedded language depends on the specific use case and the trade-offs you are willing to make in terms of size, performance, and features.

  3. User

    There is lot of talks that ICCCM and EWMH protocols for window managers on Linux are kinda bad and it's support is not good. Why and what happened?

  4. Assistant

    The ICCCM (Inter-Client Communication Conventions Manual) and EWMH (Extended Window Manager Hints) are protocols that define how window managers and applications interact on the X Window System used by Linux and other Unix-like systems. While these protocols have been traditionally used, there are several reasons why they are considered problematic or lacking in certain areas:

    1. Complexity: The ICCCM and EWMH protocols have grown more complex over time, making them difficult to understand and implement correctly. This complexity often leads to inconsistencies and interoperability issues between different window managers and applications.

    2. Lack of updates: The X Window System and its associated protocols have been around for several decades, and the ICCCM dates back to the late 1980s. The lack of major updates and modernization has resulted in outdated and insufficient support for newer desktop environments and evolving user expectations.

    3. Limited functionality: The ICCCM and EWMH protocols do not provide rich and standardized mechanisms for handling modern window management features such as desktop notifications, taskbar behavior, application launchers, or dynamic workspace management. As a result, workarounds and non-standard extensions have been developed by different window managers, leading to fragmentation and inconsistent behavior across different systems.

    4. Fragmentation and non-compliance: Due to loosely defined parts of the protocols and the lack of strict adherence to the standards, different window managers and applications often implement them differently or even deviate from them entirely. This fragmentation hampers interoperability and causes compatibility issues.

    To address these shortcomings, various efforts have been made to improve window management on Linux, such as the development of alternative display systems like Wayland and protocols like XDG Shell. These aim to simplify the standards, provide better support for modern use cases, and improve the overall user experience. However, transitioning from established protocols to new standards can be a slow process, as it requires widespread adoption and support from both desktop environments and applications.

  5. User

    Is X11 still updating? Where it's repository?

  6. Assistant

    Yes, X11 is still being updated and maintained, although the pace of development has significantly slowed down over the years. The X.Org Foundation is currently responsible for the development and maintenance of the X Window System. The X.Org Server is the official reference implementation of the X11 protocol.

    The source code for X.Org Server can be found on the official X.Org Git repository, hosted on Freedesktop.org. The repository can be accessed at:

    URL: https://gitlab.freedesktop.org/xorg/xserver

    The X.Org community consists of developers and contributors who actively work on the development and improvement of X11, fixing bugs, adding new features, and ensuring compatibility with modern hardware and software systems.

    It's worth noting that while X11 is still being updated, there is a newer display server protocol called Wayland, which is designed to address some of the limitations and issues of X11. Wayland offers improved performance, security, and better support for modern hardware and compositing effects. However, X11 continues to be widely used and supported in many Linux distributions and desktop environments.