Game developer and artist.

Spoken languages: Hu, En, some Jp

Programming languages: C, C++, D, C#, Java

Mastodon: @ZILtoid1991

Github: https://github.com/ZILtoid1991

  • 2 posts
  • 27 comments
Joined 3 years ago
Cake day: June 12th, 2023
  • Also GPU drivers.

    If you’re mad at NVidia for their closed-source drivers, then remember that ARM seldom makes their Linux drivers available for free, so you have to either have to deal with absolutely no GPU driver while the CPU does the graphics rendering (might not be a big deal on a NAS though), or with open source drivers that are less capable than the Nouveau drivers and even fiddlier to install. The ARM Mali driver issue is so bad I was legit thinking on a solution to run the Android binary blobs (which at least are available by ripping them off from the Android kernel) on regular Linux, a lot of function call redirects would likely take care of that issue.

The official documentation isn’t 100% clear on things (why am I getting LUA_TNIL for functions?), and the best I can find with some simple web search is kinda relevant stackoverflow (🤮) posts, except they’re mostly about calling host functions from Lua side, the rest are things that seem I’ve nailed so far.

EDIT: Solution was that everyone was using luaL_dofile, while I was forward thinking and used lua_load instead, which isn’t a macro, and as such doesn’t do an initial lua_pcall. Now I do it manually, and now I get different, but less cryptic and actually documented errors. Now I just have to wrestle with D metaprogramming features (very strong and capable, but is a rabbit hole itself).

  • Depends on what you’re doing. Functional programming has its own downsides, especially once you want to write interactive programs, which often depend on global states. Then you either have to rely on atoms, which defeat the purpose of the functional programming, or pass around the program state, which is janly and can be slow.

    I personally go multi paradigm. Simpler stuffs are almost functional (did not opt for consting everything due to performance issues), GUI stuff is OOP, etc.

After a software update, VS2022 stopped working correctly. When I hit a break point, I don’t get any local variables and their values, instead I get a “wait…” label that looks like a button, and also VS is growing in memory size until it crashes my Windows, or I either stop the debugging or VS itself.

So far I get the best results by using x64dbg, but it has it’s own issues, namely that almost all guides only discuss its reverse engineering capabilities, and I need a development tool, so I don’t have to rely on printing to the console as debugging, which has a lot of issues (leaving in the print commands, etc). I’m programming in D, but it should work with any other debugger made for C, and up until recently I used VS for that purpose.