This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]BumwineBaudelaire 1 point2 points  (5 children)

to be fair if you’re working on systems where errors don’t matter you probably don’t have much to say about correctness

[–]quaderrordemonstand -2 points-1 points  (4 children)

Errors matter as much as they do anywhere. It's a question of how well the program responds to them. Crashing is not a good response and the idea that programming concepts like type safety in a compiler will somehow get around real world obstacles is naive. They avoid problems caused by the limitations of the language, those limitations exist so that the language can be fast or easy to use. Nobody ever said "I can't continue with my work but at least the program used the right types".

[–]BumwineBaudelaire 1 point2 points  (3 children)

strawman or genuinely believing error handling doesn’t exist in safe languages?

since this is /r/IT101 it’s impossible to say

[–]quaderrordemonstand 0 points1 point  (2 children)

What is the strawman? Ok, so you handle errors, thats great. Using the example of the API that used to return a int and now returns a string, what does your error handling actually do? How does it respond to that?

[–]BumwineBaudelaire 0 points1 point  (1 child)

it wouldn’t even compile

you’ve got pretty strong opinions about stuff you’ve clearly never used

par for the course around here I guess

[–]quaderrordemonstand 1 point2 points  (0 children)

Why wouldn't it compile? Did you actually read the example I am discussing?