this post was submitted on 17 Oct 2024
922 points (98.9% liked)

RetroGaming

19338 readers
1302 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
Xylinna@lemmy.world
Tenthrow@lemmy.world
gts@lemmy.world
922
How hard could it be? (lemmy.world)
submitted 17 hours ago by The_Picard_Maneuver@lemmy.world to c/retrogaming@lemmy.world
89 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] einlander@lemmy.world 91 points 13 hours ago (1 children)
  • Programming was never meant to be abstract so far from the hardware.
  • 640k is enough ram for everybody.
  • The come with names like rust, typescript, go, and python. Names thought up by imbeciles.
  • Dev environments, environmental variables, build and make scripts, and macros, from the minds of the utter deranged.

They have played us for fools

[โ€“] mynameisigglepiggle@lemmy.world 2 points 1 hour ago

I dabbled with making a fairly complex program for a microcontroller the other day and quickly hit the stack limit for a simple object.

It wasn't so much that it was a large object, but to provide flexibility I was amazed how fast I filled the memory.

I've done heaps with memory managed languages in the past but shit as soon as I had to think about what I was doing under the hood everything got hard af.

So serious question - does anyone have any good resources for a competent programmer, but with no clue whatsoever how to manage memory in a microcontroller space and avoid fragmentation etc?

I got it to work but I'm sure I did shit job and want to be better at it.