Programming

17378 readers

521 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 !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

104

[History] An editor letter by Edsger Dijkstra, titled: "go to statements considered harmful" (march 1968). (dl.acm.org)

submitted 5 months ago by abbadon420@lemm.ee to c/programming@programming.dev

58 comments fedilink hide all child comments

In this letter, Dijkstra talks about readability and maintainability in a time where those topics were rarely talked about (1968). This letter was one of the main causes why modern programmers don't have to trouble themselves with goto statements. Older languages like Java and C# still have a (discouraged) goto statement, because they (mindlessly) copied it from C, which (mindlessly) copied it from Assembly, but more modern languages like Swift and Kotlin don't even have a goto statement anymore.

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

[–] 0x0@programming.dev 3 points 5 months ago (1 children)

When your CPU clock is measured in megahertz, your RAM is measured in kilobytes

Ah yes, the good ol' days when developers programmed for efficiency.

[–] atzanteol@sh.itjust.works 3 points 5 months ago (1 children)

Mostly because they had to. Writing efficient code and easy-to-read code are often at odds with each other. I like being able to create lots of functions that can be called from a loop without needing to worry too much about function call overhead. I can prioritize readability for some time before I ever need to worry about performance.

[–] 0x0@programming.dev 1 points 5 months ago (2 children)

I get that but it seems as though no one cares at all about efficiency these days.

[–] atzanteol@sh.itjust.works 2 points 5 months ago

People have been complaining about this exact thing forever. Even back when "people cared about efficiency".

[–] BatmanAoD@programming.dev 1 points 5 months ago

Does the catchphrase "blazing fast" ring any bells? Some people care.

(Arguably that's just the pendulum swinging the other way; Ruby, Python, and Java ruled the software world for a while, and I think that's a large part of why the Go and Rust communities make such a big deal about speed.)