Programming

16769 readers

76 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

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 [email protected]

founded 1 year ago

MODERATORS

[email protected]

104

What are some common misconceptions about programming that you'd like to debunk? (programming.dev)

submitted 6 months ago by [email protected] to c/[email protected]

167 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 15 points 6 months ago (1 children)

that doing more work, takes more time.

Gamers are especially guilty of this.

"that 2013 game runs at a smooth 60 fps. This medern game running at quadruple the resolution with raytracing sometimes dips to 58 fps on the same hardware. Devs must be lazy, they just need to add OPTIMIZATION to the game

[–] [email protected] 0 points 6 months ago

I don't know what it's called, but it's a common phenomenon: available room will be exploited. It's exactly why computers nowadays don't feel faster than computers from a decade or two ago: they do so much more because they can.

Stuff like electron would've been impossible in 2000 or 2005: it's just a behemoth in terms of computational needs and power consumption. Earlier computers would've struggled endlessly with it. Current hardware however makes it seem as fast as previous tech.

CC BY-NC-SA 4.0