806
The coding experience
(b.l3n.co)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 Oct 2023
806 points (93.6% liked)
Programmer Humor
32561 readers
383 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
Well, I'm not just talking about issues.
This sounds like they did not or could not explicitly compile it. Pretty much all popular languages are compiled. JS isn't, but people are less likely to say that they 'run' that one. Ruby isn't, but it's not as popular as Python.
Well, and my preferred version of "everything looks good" is "everything compiles", which with a strict enough language does also make failure during the first run much less likely.
I'm also not saying that these aspects are unique to Python.
The language failing to tell you where the issue is also happens in JS/TS, C/C++ and I'm going to presume Ruby, too.
Python is just again rather popular and some of these choices don't make sense with my first hunch.
Honestly man it just sounds like you have struggled with dynamic languages and by extension prefer static (compiled) ones. Which is totally fine you don't have to like everything. But I do think you're missing the real issue with "everything looks good." It's a lack of experience with the tool. It doesn't matter if you're using something as strict as Rust or dynamic as Lisp. "Everything looks good," is always bad. You should know "this is how this works," which is just not something a newbie can handle when they still don't know the difference between pass-by-reference and pass-by-value (or that those words even exist!)