• Abyssian@lemmy.world
    4·
    2 hours ago

    The circle is now complete. It began with coding in raw machine language, and it ends in coding entirely in emojis. The prophecy has been fulfilled. The end is nigh.

    Somebody set up us the bomb. All our base are belong to them. You have no chance to survive make your time. Move ‘ZIG’.

  • Zarobi@aussie.zoneEnglish
    62·
    10 hours ago

    For some reason the inclusion of this emoji sends me

    🫪

    🫪

    🫪

    🫪

    🫪
    🫪

    🫪

    ~🫪~

  • Yaky@slrpnk.net
    16·
    8 hours ago

    This reminds me of “bugoga” from the olden days.

    (Circa 2007 on bashorgru, there was a meme about writing “bugoga” into a text file, renaming it to exe and then running it. That made the cursor jump around the console and if you had a connected matrix printer, it would start going crazy - something about writing spaces to all available output in an endless loop)

    • monotremata@lemmy.caEnglish
      4·
      1 hour ago

      It kind of reminds me of a thing from the Apple IIe. If you were running a program on that machine and it crashed, it would often crash into this built-in micro debugger mode that gave you a * prompt. The normal boot-up ] prompt accepted BASIC and PRODOS commands, but the * prompt was for working with the Apple microassembler, and it was NOT user-friendly to the average young geek. So I learned exactly one command, which was 3D0G. My understanding was that this was an unconditional jump command to the place that PRODOS was normally loaded into memory at boot, so if the program hadn’t overwritten that, it would get you back to the ] prompt. (Otherwise you had to turn the computer off and on again so it would reload from ROM, which wasn’t a huge problem anyway, but this was a bit faster.) But I’m not actually sure exactly what it did. Anyway, it was memorable enough (since the zero looked close to an O that I could remember it as “three dogs”) that I held on to it. Not actually important, just, y’know, kinda fun.

    • black0ut@pawb.social
      67·
      12 hours ago

      Yeah. This method is really cool, and it has been used for legitimate cases before. Look at the EICAR file:

      X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*

      It is a test file for malware detection software (in fact, it will still get flagged today if you try to send it, download it or save it to your disk). It prints “EICAR-STANDARD-ANTIVIRUS-TEST-FILE!” when run.

      It was purposefully made so all the opcodes appeared as characters you can type on a standard keyboard. That way, anyone can write the file themselves even if they don’t have internet or a way to download it. It’s also easier to get it into test containers/VMs that are isolated from the internet or physical hardware, which is where most malware testing happens.

  • angband@lemmy.world
    8·
    11 hours ago

    Edlin and debug allowed fast com file programming.

    🐸☺️🐰🐎♐🗃️🧯🧯🧯🐮💗🦮🪏♐🐰🐹🗃️🧯🧯🧯🧯💗🪗🧯😗🧮🫪😗🧮😗🐮😪😔⭐

    But that’s neat.

  • LumpyPancakes@piefed.socialEnglish
    9·
    12 hours ago

    I vaguely recall that typing ‘copy con clock$’ would freeze a computer.

    On DOS you could also have fun by replacing prompt $p$g with prompt {whatever text you want instead of c:}

    • zurohki@aussie.zoneEnglish
      17·
      11 hours ago

      On DOS you could also have fun by replacing prompt $p$g with prompt {whatever text you want instead of c:}

      • LumpyPancakes@piefed.socialEnglish
        12·
        11 hours ago

        Righto :)

        I was a DOS ‘programmer’ long before I migrated to Linux - the same way some guy who used to write bat files with environment variables and errorlevel commands might migrate to a shell script.

        What I really wanted was to be able to embed ^g into the Linux command line prompt, but so far I haven’t been able to. On DOS I could add ^g (the Bell character) to the prompt so each time a command finished it beeped.

        • balsoft@lemmy.ml
          7·
          8 hours ago

          I have a slightly more advanced setup which uses post-command hooks to send a desktop notification when a command has been running for over 3 seconds. That notification contains the elapsed time and the exit code too, and plays a different sound depending on whether the command was successful or not. This allows for some neat integrations with KDE connect to let me know when some long compile has finished or something even when I’m away from my computer. You can see how it works here.

        • Droechai@piefed.blahaj.zoneEnglish
          7·
          11 hours ago

          I had to do some really wacky stuff but I finally got all manner of beeps and boops from the motherboard speaker last month (aftermarket addon). Stuff like beep on startup, buzz when moving a window, different quick peeps when clicking, doubleclicking or right clicking. I had it for about an afternoon and then my partner raged at all the noise :/ now my computer are silent and boring again

          • LumpyPancakes@piefed.socialEnglish
            4·
            9 hours ago

            Now you need a proximity sensor to mute it only when your partner is nearby :)

            Mine is still tolerating my "Eddie Izzard covered in bees person on the street reaction sound’ sms notification sound.