• 2 Posts
  • 216 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle




  • addie@feddit.uktoMicroblog Memes@lemmy.worldMasochism
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    1
    ·
    10 days ago

    EZ mode in Elden Ring is to play Scadow of the Erdtree for a bit. That hands out fifty level-ups for shitting yourself hiding in the bushes, just to mock you for how you still ain’t got gud. Go back and beat up Malenia and Placidusax all you want, you’re still going to die to the very first expansion boss like you’ve never played a Souls game before.










  • Most of the laptops I’ve had open lately have had about the top third be the motherboard and the bottom two-thirds be battery, with maybe some ports and speakers tucked down the side. So I’d expect that last of replacements to include the battery, too.

    I might check whether the hard drive survived - a decent M.2 is small, expensive and reusable - and maybe the RAM if it’s not soldered in.




  • Having had one of the old Windows phones with a keyboard dumped on me at an old workplace, can confirm it’s completely possible for a phone to have a keyboard and be a complete piece of shit.

    A good phone with a good keyboard may have some use cases. If you do a lot of writing but not any more computing power or screen space than a phone has, plus you want to be doing that on the move, then yeah. For me, can shitpost on forums using my phone in my spare time, and dealing with on-call work issues - having multiple tabs of Jira and Slack open, for instance - just isn’t really practical on a small screen.

    If your job is very email-centric, then yeah, sure. Blackberry were very good for just having the stuff you need - email, vpn, ‘corporate’ office documents - in a form that worked.




  • addie@feddit.uktoRetroGaming@lemmy.worldHow hard could it be?
    link
    fedilink
    English
    arrow-up
    52
    ·
    2 months ago

    Writing in ASM is not too bad provided that there’s no operating system getting in the way. If you’re on some old 8-bit microcomputer where you’re free to read directly from the input buffers and write directly to the screen framebuffer, or if you’re doing embedded where it’s all memory-mapped IO anyway, then great. Very easy, makes a lot of sense. For games, that era basically ended with DOS, and VGA-compatible cards that you could just write bits to and have them appear on screen.

    Now, you have to display things on the screen by telling the graphics driver to do it, and so a lot of your assembly is just going to be arranging all of your data according to your platform’s C calling convention and then making syscalls, plus other tedious-but-essential requirements like making sure the stack is aligned whenever you make a jump. You might as well write macros to do that since you’ll be doing it a lot, and if you’ve written macros to do it then you might as well be using C instead, since most of C’s keywords and syntax map very closely to the ASM that would be generated by macros.

    A shame - you do learn a lot by having to tell the computer exactly what you want it to do - but I couldn’t recommend it for any non-trivial task any more. Maybe a wee bit of assembly here-and-there when you’ve some very specific data alignment or timing-sensitive requirement.