1384
How hard could it be? (lemmy.world)
submitted 2 years ago by to c/retrogaming@lemmy.world
174 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 38 points 2 years ago (1 child)

I mean, I'm pretty sure it would be a good learning experience so I would really not regret it.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 31 points 2 years ago (3 children)

    I tried decades ago. Grew up learning BASIC and then C, how hard could it be? For a 12 year old with no formal teacher and only books to go off of, it turns out, very. I've learned a lot of coding languages on my own since, but I still can't make heads or tales of assembly.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 23 points 2 years ago (1 child)

    Assembly requires a knowledge of the cpu architecture pipeline and memory storage addressing. Those concepts are generally abstracted away in modern languages

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 12 points 2 years ago* (1 child)

    You don’t need to know the details of the CPU architecture and pipeline, just the instruction set.

    Memory addressing is barely abstracted in C, and indexing in some form of list is common in most programming languages, so I don’t think that’s too hard to learn.

    You might need to learn the details of the OS. That would get more complicated.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 7 points 2 years ago

    I said modern programming languages. I do not consider C a modern language. The point still stands about abstraction in modern languages. You don’t need to understand memory allocation to code in modern languages, but the understanding will greatly benefit you.

    I still contend that knowledge of the cpu pipeline is important or else your code will wind up with a bunch of code that is constantly resulting in CPU interrupts. I guess you could say you can code in assembly without knowledge of the cpu architecture, but you won’t be making any code that runs better the output code from other languages.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 9 points 2 years ago (1 child)

    Try 6502 assembly. https://skilldrick.github.io/easy6502/

    My favorite assembly language by far.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    this page is great. starting right at "draw some pixels" in such a simple way just instantly makes it feel a bit more approachable!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 2 years ago (1 child)

    Sounds very similar to my own experience though there was a large amount of Pascal in between BASIC and C.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 2 years ago (1 child)

    Yeah, I skipped Pascal, but it at least makes sense when you look at it. By the time my family finally jumped over to PC, C was more viable. Then in college, when I finally had to opportunity to formally learn, it was just C++ and HTML... We didn't even get Java!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago

    I had used like four different flavors of BASIC by the time I got a IBM compatible PC, but I ended up getting on the Borland train and ended up with Turbo Pascal, Turbo C, and Turbo ASM (and Turbo C++ that I totally bounced off of). I was in the first class at my school that learned Java in college. It was the brand new version 1.0.6! It was so rough and new, but honestly I liked it. It's wildly different now.

  • permalink
  • fedilink
  • source
  • parent