this post was submitted on 19 May 2024
102 points (97.2% liked)

Programming

16311 readers
184 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 1 year ago
MODERATORS
 

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
[–] atzanteol@sh.itjust.works 4 points 1 month ago (5 children)

Java does not support goto.

[–] mrkite@programming.dev 3 points 1 month ago (3 children)

And yet it's still easy to write spaghetti code in Java. Just abuse inheritance. Where is this function implemented? No one knows but the compiler!

[–] 0x0@programming.dev 4 points 1 month ago

You mean SpaghettiFactory()

[–] SatouKazuma@ani.social 3 points 1 month ago

And don't forget to use miracle sort for any sorting needs you have. Why do the work yourself when you can just hope it gets solved for you?!

[–] warlaan@lemm.ee 0 points 1 month ago

That doesn't make it spaghetti code though. In well-written OOP code you shouldn't care where a function is implemented. The problem is a much too high level of abstraction. If your high level code is so abstract that it is only running tasks and handling messages there's no way to write it in a way that prevents mistakes because you couldn't possibly know what the actual implementations do.

load more comments (1 replies)