this post was submitted on 22 Dec 2023
31 points (91.9% liked)
Programming
17528 readers
313 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Gosh I hope to hell you're being sarcastic because that's one of the worst takeaways you could probably get.
Technically, for performance, machine code has a higher performance ceiling than code produced by a compiler... but it's so fucking likely that you're going to make an error, either logically or in terms of performance, that machine compiled code almost always out performs hand written assembly written by gurus.
In terms of goto vs. for... gotos make it extremely easy to accidentally leave or enter functions without pushing or popping the appropriate frames so it's highly likely you'll end up introducing a really hard to track down segfault... there are better excuses you can find to learn
gdb.