this post was submitted on 17 Oct 2024
1007 points (99.0% liked)

RetroGaming

19338 readers
1642 users here now

Vintage gaming community.

Rules:

  1. Be kind.
  2. No spam or soliciting for money.
  3. No racism or other bigotry allowed.
  4. Obviously nothing illegal.

If you see these please report them.

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
1007
How hard could it be? (lemmy.world)
submitted 20 hours ago by [email protected] to c/[email protected]
101 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 19 points 7 hours ago* (last edited 7 hours ago) (1 children)

To further emphasize this, I had an assembly course in university. During my first lab, the instructor told us to add a comment explaining what every line of assembly code did, because if we didn't, we would forget what we wrote.

I listened to his advice, but one day I was in a rush, so I didn't leave comments. I swear, I looked away from the computer for like 2 minutes, looked back, and had no idea what I wrote. I basically had to redo my work.

It is not that much better than reading 1s and 0s. In fact in that course, we spent a lot of time converting 1s and 0s (by hand) to assembly and back. Got pretty good at it, would never even think of writing a game. I would literally rather create my own compiler and programming language than write a game in assembly.

[–] [email protected] 13 points 7 hours ago (2 children)

I'm probably completely insane and deranged, but I actually like assembly. With decent reverse engineering software like Ghidra, it's not terribly difficult to understand the intent and operation of isolated functions.

Mnemonics for the amd64 AVX extensions can go the fuck right off a bridge, though. VCVTTPS2UQQ might as well be my hands rolling across a keyboard, not a truncated conversation from packed single precision floats into packed unsigned quadword integers.

[–] [email protected] 1 points 2 hours ago* (last edited 2 hours ago)

Ah yes, there was this guy in our tech school class that used to code golf in assembly. Was a crack in math and analytics too, which might explain it somewhat. Well, everyone is different i guess.

[–] [email protected] 9 points 7 hours ago (1 children)

I had a course in uni that taught us assembler on z/os. My advisor told me most students fail the course on the first try because it was so tough and my Prof for that course said if any of us managed to get at least a B in the course, he'd write us a rec letter for graduate school. That course was the most difficult and most fun I've ever had. I learned how to properly use registers to store my values for calculations, I learned how to use subroutines. Earned myself that B and went on to take the follow up course which was COBOL. You're not crazy, I yearn to go back to doing low level programming, I'm mostly doing ruby for my job but I think my heart never left assembler hahaha