• 0 Posts
  • 17 Comments
Joined 3 years ago
cake
Cake day: June 27th, 2023

help-circle

  • I used the github copilot tui (since that was what my subscription was through) and told it what the devices were and what I was trying to accomplish. From there it was a mixture of different things to figure out how the protocols worked, like running the apps in wine and having it log and capture data as I changed settings, or have it flip bits and I would report to it what changed. If it discovers a component in the device is something off-the-shelf, have it find reference material from the component manufacturer.

    As you figure out how a particular protocol works you have it document it until you have everything you need to build your own CLI to interface with the device. At that point you have a pretty good idea of how the device works and it’s capabilities and you can build out whatever features you want around it.




  • Resource management comes in many different flavors. Most computers allow you to use every resource it has at its disposal to accomplish a task (rendering graphics, processing workloads, gaming, etc), and that would really suck to have your system just decide it should nuke that process. It doesn’t really know what you prioritize, so Instead it runs and compromises the best it can until the dam breaks. But gaming is a little less of a gray area, its nearly always the main focus of the user, so its easy to draw a line there.

    There are systems that are far more opinionated about resource usage that will reign in processes. Like iOS is a good example (The divide is usually desktop and mobile OSs). It prioritizes UI, battery life, and animation fluidity over any process and will kill anything that threatens it.

    There are applications out there you can use to limit resource usage per app, so you can limit the resources of bloated browser engines that masquerade as native apps.




  • I needed a new vehicle this year and knew I wanted a small truck to help with my forever ongoing home renovation needs. A Ranger was definitely what I was targeting before ultimately falling in love with an 88 Jeep Comanche long bed. Perfect size truck that looks Comically small when parked next to any modern day truck





  • Like what? And is that a common use case?

    Furniture is what comes to mind

    Or just put down a nylon sheet, put the dirt on top, fold the nylon sheet over it and bind it down. … Buy a bus with removable carpet, then you can just hose it down as well.

    Sure, you could do that, or you could use the right vehicle for the job.

    There are many different rear door types and sliding side doors on the side that provide ample and easy access. This isn’t difficult or complicated.

    Until you want a pallet of something. Would be nice if that van had a removable roof so they could just drop it in there 😉

    What it comes down to is that trucks are versatile and people like them for it. If you don’t see utility in having open access, then that’s fine, but a lot of people do.


    • Sometimes you need to move a thing that is oddly shaped and doesn’t fit within the confines of an enclosure
    • Depending on what you’re hauling, you may want separation between the cab and the payload. Like if I’m moving dirt, I’d rather not have it rolling around my cabin
    • Easier to clean, just take a hose to it without needing to worry about soaking the cabin
    • Access isn’t limited to just the door, which can be useful when unloading something



  • I think that is what made that battle system interesting: More focus on delegation over micro management.

    The main portion of the battle played outside of the battles themselves and was all about how you essentially “programmed” these workflows for each character to work in harmony together to win battles. You could get in the fray to fix any unintended outcomes of these flows, but was mainly to observe the outcomes and make adjustments.