12

WHY IS IT SO FUCKIN ABSURDLY HARD TO PUSH BITS/BYTES/ASM ONTO PROCESSOR?

I have bytes that I want ran on the processor. I should:
1. write the bytes to a file
2a. run a single command (starting virtual machine (that installed with no problems (and is somewhat usable out-of-the-box))) that would execute them, OR
2b. run a command that would image those bytes onto (bootable) persistent storage
3b. restart and boot from that storage

But nooo, that's too sensible, too straightforward. Instead I need to write those bytes as a parameter into a c function of "writebytes" or whatever, wrap that function into an actual program, compile the program with gcc, link the program with whatever, whatever the program, build the program, somehow it goes through some NASM/MASM "utilities" too, image the built files into one image, re-image them into hdd image, and WHO THE FUCK KNOWS WHAT ELSE.

I just want... an emulator? probably. something. something which out of the box works in a way that I provide file with bytes, and it just starts executing them in the same way as an empty processor starts executing stuff.

What's so fuckin hard about it? I want the iron here, and I want a byte funnel into that iron, and I want that iron to run the bytes i put into the fuckin funnel.

Fuckin millions of indirection layers. Fuck off. Give me an iron, or a sensible emulation of that iron, and give me the byte funnel, and FUCK THE FUCK AWAY AND LET ME PLAY AROUND.

Comments
  • 3
    You want an old CPU. :)
  • 3
    Buy a 6502 (they actually still produce them) and experiment. Ben Eater has a bunch of cool and useful tutorials on how to make that happen, I recommend
  • 1
    You need one of these
  • 1
    @shoop Yes, Ben Eater's videos are really useful on this
  • 2
    Quality rant!
    I can feel the rage, and it makes me want more 🙂

    Also: fuck the thousands of layers of abstraction and processing and indirection and goddamn bullshit! 😡😡😡
  • 3
    @Root Only Garfield can like this amount of lasagna....
  • 0
    Erm. Sorry whats the problem again? Your three step process works for me.
  • 2
    grab an EEPROM writer, write your code to it, snap onto processor board, go.
    Wait, emulator?

    compile to bytecode, grab a VHD, mount it, write in bytecode raw starting from sector 0 byte 0 or whatever address your CPU is told/defaulted to run from, unmount, mount VHD in DOSBox or QEMU or whatever other gay shit, boot. Code always either starts at 0000 or some location, definable or not.

    RTFM, and specify what processor.
  • 0
    @kescherRant no, i want x64 cpu, because that's where i want my thing to run
Add Comment