• 1 Post
  • 87 Comments
Joined 3 years ago
cake
Cake day: March 25th, 2022

help-circle








  • At least with hexbear you should be able to stop any further responses by stating within the comment that you wish to disengage from the conversation.

    https://hexbear.net/code_of_conduct :

    Any discussions may be opted out of by disengaging

    However, do not add anything else as hexbear’s disengage rule only applies if you don’t use it to have the last word in the matter.

    Also, while some hexbear posts may sometimes contain nudity (though I have never seen any pornography on there and it’s probably not even allowed), it should be labeled as such. Anything potentially triggering or unwanted should have content warnings in the title.











  • Faresh@lemmy.mltoRetroGaming@lemmy.worldHow hard could it be?
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    2 months ago

    you’re not usually directly accessing/working on the hardware

    I mean, you are. Sure, there’s a layer of abstraction when doing tasks that require the intervention of the kernel, but you are still dealing with cpu registers and stuff like that. Merely by writing in assembly you are making your software less portable because you are writing for a specific ISA that only a certain family of processors can read, and talking with the kernel through an API or ABI that is specific to the kernel (standards like Posix mitigate the latter part somewhat, but some systems (windows) aren’t Posix compilant).