(_____(_____________(#)~~~~~~

  • 2 Posts
  • 86 Comments
Joined 3 years ago
cake
Cake day: April 11th, 2022

help-circle

  • Older Hardware can be pretty decent if you know what you’re doing. However, many projects (even FOSS that are more hobbyist) are making decisions that make their software harder to use on older hardware. For example, everyone’s desire to switch to zstd is terrible for people on older hardware, since it was designed around more recent CPUs. It’s noticeably slower for little gain on older hardware, yet they love to parrot the “That’s just how progress goes”-line while shoving highly curated benchmarks into people’s faces to “prove” that $LATEST_THING from silicon valley is “superior”.

    Arch Linux used to be really snappy on all of my Hardware out of the box before they went all in on zstd. Now I have to go out of my way and put in a bunch of work just to get back at least most of that performance.



  • Even if Lemmy was run by a piece of shit, anyone could just modify the source code and make their own version. Plus, Lemmy is an implementation of the ActivityPub Protocol, and there are many Projects out there that speak ActivityPub: https://fediverse.party/

    You can think of ActivityPub as being similar to E-Mail; It’s not like Gmail Accounts can’t send messages to Accounts on Outlook or vice versa, they can, because they both speak a common Protocol that predates both of those Providers.

    People on Mastodon or Pleroma Instances can follow Communities on Lemmy and can read, favorite or repost Posts like this one.




  • Packaging legacy drivers isn’t really a solution. I have a literal stack of older NVidia Cards (some are even Quadros) that are just Paperweights because:

    • NVidia’s Proprietary drivers suck dick and were never really good.
    • Since the NV Driver is Proprietary, you’ll be stuck on an ancient version of Linux or FreeBSD (the Kernel version that NVidia compiled it for).
    • Forget Vulkan, OpenCL, Wayland and decent Hardware Video Decoding support unless you’re lucky and your “legacy” card is recent enough for the driver to support at least some of those.

    I’m really annoyed by how FreeDesktop/Nouveau developers only keep chasing the “latest and greatest” when there is a lot of existing Hardware out there that has only had half-assed support for at least a decade, but for some reason no one cares. Seriously, everytime I read about updates related to Nouveau or Mesa it’s never about older Hardware anymore.













  • Years ago I wrote a VN engine from scratch in C++ that never got finished, for a project that never came to be. It had some developer tools (some of which never got fully realized): One where you could manage your Assets in the Game’s Pack file and one where you could create and edit GUIs. I made my own basic scripting language for it which I used not only for scenes but also for all the UI. It was kind of powerful, but in my script I didn’t have any nodes only “functions” which were really just a set of instructions for the engine, and branching decisions would just call out to other “functions” (which could live in other files even).

    Not sure what to think of the more data-oriented approach here, I feel like it could get a little messy with the “choices” array. I would make the “type” an Integer instead of a String, and the “character” and “speaker” seem a little redundant, unless one is supposed to be like an ID, in which case I would come up with a better naming convention (like “main_anna” or something like that).