HiddenLayer555@lemmy.ml to Programming Humor@lemmy.worldEnglish · 1 year agoThey're trying to normalize calling vibe coding a "programming paradigm," don't let them.lemmy.mlimagemessage-square12linkfedilinkarrow-up193arrow-down13cross-posted to: programmer_humor@programming.devprogrammerhumor@lemmy.ml
arrow-up190arrow-down1imageThey're trying to normalize calling vibe coding a "programming paradigm," don't let them.lemmy.mlHiddenLayer555@lemmy.ml to Programming Humor@lemmy.worldEnglish · 1 year agomessage-square12linkfedilinkcross-posted to: programmer_humor@programming.devprogrammerhumor@lemmy.ml
minus-squarebarsoap@lemm.eelinkfedilinkEnglisharrow-up4·1 year agoLess of a paradigm but a way to write exploits but still more of a paradigm than vibe coding. It basically means “hey I can buffer overflow over the return address, let’s treat the program’s code as a VM to do what I want”.
minus-squareLoaf@sh.itjust.workslinkfedilinkEnglisharrow-up1·1 year agoWow, I never even knew about ROP until today. I feel kind of silly 😅 This is interesting, but I don’t think I could find a genuine use-case for it.
Less of a paradigm but a way to write exploits but still more of a paradigm than vibe coding. It basically means “hey I can buffer overflow over the return address, let’s treat the program’s code as a VM to do what I want”.
Wow, I never even knew about ROP until today. I feel kind of silly 😅
This is interesting, but I don’t think I could find a genuine use-case for it.