I’m a software engineering developer from Ottawa, Ontario, Canada.

  • 0 Posts
  • 6 Comments
Joined 2 years ago
cake
Cake day: June 6th, 2023

help-circle

  • Lambda@lemmy.catoLinux Gaming@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    25
    ·
    6 months ago

    Sadly front end, like “High Level” is a very relative term. For example, in compiler design, the bit that parses code is called the “front end” since the “back end” is what emits machine code. I think that’s what they mean here, the “front end” that understands D3D8 code has been added, presumably there is also a “back end” that converts the parsed/analyzed D3D8 code into valid opcodes for consumption by GPU/CPUs.

    In the other direction, a UI/UX is sometimes called a “back end” when it is part of a more complex embedded project where physical controls are the “front end”.




  • Yeah, that’s pretty much what I was thinking too. The combination of a c API and a JVM API (and maybe .NET if you’re in Microsoft land?) Hits most FFI available in languages I’ve seen. I can’t think of any language I’ve used that couldn’t Interop with either a c library (.a or .so) or JVM library (.jar). However I’ve never used any .NET system seriously, so I don’t know about them.

    FWIW I regularly remake the same API based game whenever I start a new job working in a new environment to test that my environment is “up to snuff” with my development methodologies. I’ve never needed to port more than API.a and API.jar to play around in any language. I’ve ported that system to at least 100 languages over the years, and while some have more friction than others, and often the c/JVM paradigm doesn’t line up well with the target language, it is always effective.