This is sometimes practical, too. For example, hooking and extending functions in compiled code that will never be updated by the original author, while preserving the original executable/library files.

Your original comment made it seem more like extensions - extend and preserve. That's the misunderstanding.

When I said it's wild to manipulate bytecode I means "wow that's a terrifying practice, I would hate to check that PR"

[–] mox@lemmy.sdf.org 1 points 7 months ago* (last edited 7 months ago) (1 children)

Fair enough. What threw me is that you said "bytecode", which is generally not used when referring to hardware machine instructions. My original comment is about patching the in-memory image of a running program or library, replacing machine instructions in order to intercept certain calls and extend their behavior.

I thought my phrase "compiled code" would convey this, but I guess nowadays bytecode-compiled languages are so common that some people assume that instead.

[–] huginn@feddit.it 1 points 7 months ago (1 children)

Yeah and part of this is that the domain I've been working in for years now is very far from machine code, and I'm probably overly lax with my language here.

The result of being in very corporate app dev - I'm usually talking in much higher level abstractions. My bad on conflating bytecode and machine code

[–] mox@lemmy.sdf.org 2 points 7 months ago (1 children)

Ah, corporate work. I hope they're treating you well.

[–] huginn@feddit.it 1 points 7 months ago

Different strokes - some would find what I'm doing hell. I personally love it.

The 260k/yr salary may help alleviate the pain.