[–] 1 point 5 months ago

I guess what I'm trying to get at is, a game engine contains a 3D (or 2D) renderer, but that's not its sole focus. There are other projects which are just that, a game engine is a lot of other things too, physics simulator, audio engine, UI framework, etc. A compositor is similar, it's a compositing window manager, a Wayland display server, an input handler, etc. It does far more than manage windows. When we look at X11 all a window manager does is manage windows, composition was a separate application, although sometimes the window manager would handle it, input handling was managed directly by the X server. Basically a Wayland compositor is a compositing window manager, and display server combined into one, it's like a game engine, calling one a 3D renderer is missing out on the vast array of other responsibilities.

  • source
  • parent
  • context
  • [–] 1 point 5 months ago (2 children)

    Yes they do but that's likely a vestigial remnant of X11 naming schemes. I could point out labwc, xfwl, hyprland, dwl, etc for counter examples. Yes compositors manage windows, they are not called window managers by the spec.

    From the Wayland website

    A Wayland server is called a "compositor".

    Additionally, there are compositors that leave window management out of their job description, I believe there are a few but the one I remember most is kiwmi which left window management to lua scripts.

  • source
  • parent
  • context
  • [–] 10 points 5 months ago (1 child)

    I'm an older weeb, dubs are the only way I'll watch, reading subtitles is exhausting and takes all the joy out of watching the show, dubs are the only reason I actually like anime

  • source
  • [–] 3 points 5 months ago

    but really we need to stop these laws from happening in the first place. I will grant that the poster does not attribute foot nor bad to the situation.

    What I think everyone is trying to tell you is that nobody is disagreeing with this sentiment. These laws are bad, I doubt the poster of the article would disagree. What is trying to be said here is if these laws go into affect (which is bad), and they exempt Linux (which seems good), they will quite possibly condemn Linux to an even smaller niche of tech nerds than it already belongs to and that is bad for Linux being a desktop platform, and it may be better for Linux to comply for its survival as a desktop platform. That is all that's being said here, nobody is arguing the merits of the laws.

  • source
  • parent
  • context
  • [–] 0 points 6 months ago

    Yes, you CAN stop there, the other qualifiers I added were specifically because C sort of assumes those to be present and while there are C to bf compilers they emulate that functionality on top of the more restrictive, but turing complete, architecture. I was listing the things C assumes/requires the hardware to be able to do for reasonable performance and compilers not emulating features.

    These are not language features but features of the C standard library and are only required if you wish to use said library, they have little to do with hardware requirements or the language itself

    You aren't wrong but classically a high level language is one that is abstracted from the hardware which is precisely why C is considered high level. You don't have to think about registers, instructions, stacks, etc, you just call functions with arguments and write "high level" code. It's on the lower end compared to modern very high level languages but it's still considered high level. Classically most non-assembly languages are.

  • source
  • parent
  • context
  • view more: ‹ prev next ›