@synthcryptid ... see I'm just reading this as a plurality joke.
... unless it is a plurality joke

@Aether

We see it now and honestly that interpretation Goes Hard

@synthcryptid @Aether what was the *intended* interpretation, because we don't see any other?
-F

@Felthry @Aether

It's how one defines a class in C# that inherits from multiple classes! Truncated for brevity, of course (Since this can only be done via interfaces, the resulting class *must* define all functions in the interfaces it's inheriting. Traditionally, this ends up being done by creating the "inherited" classes within the new class, and passing functions to either as needed). This is done to the standards of defining systems within an ECS structure (only systems can have code in ECS), and thus they are labelled accordingly.

Basically, stripping the joke down to its bare essence: Switch = Sub & Dom!

@synthcryptid @Aether what are the "system" words for then?
-F

@Felthry @Aether

Adherence to standards!~

In an ECS structure, it's expected that entities, systems, and components are strictly separated and labelled as such in their definitions for ease of clarity of what something does (entities contain only components, components contain only data, and systems contain only code!)

While writing it as though it's a part of an ECS codebase isn't entirely necessary for the joke (C# is often used for OOP, as well!), it does leave room for a Very powerful alternate interpretation!

@synthcryptid @Aether we do hardware and avoid software whenever possible, so i barely understand what you just said!
-F