why are exceptions bad? they seem to be useful, although i don't use them that often. i really dont want to watch the whole video to figure out why you should not use exceptions
Exceptions are first of all misused in software engineering. They assume that it is either good or bad (= trigger exception).
The hard reality in software you have "good", "bad" and "exception"
"False" should never be used to trigger an exception. A False may be recoverable and therefore becomes true in the whole process.
"Exceptions" should only be used on the very extreme unlikely event that your software cannot handle it. It is a situation that should actually never ever happen. If you throw exceptions then you basic design is deeply flawed. And now I have upset probably 90% of the Millennials. But I don't care. It is time to bring back good coding.
Why do exceptions "appear" to be helpful: Simple hello world applications and enterprise code that what I cal only live in a flat 2D space. You can't create complex code when you use exceptions. You can't test your code when you use exceptions. You can't recover in a simple way when you use exceptions. Exceptions will jump at some random location in your code you cannot predict.
Exceptions cause more problems then what they try to solve. get rid of using exceptions in your code and learn to develop without exceptions and I guarantee you that your code will become near zero bug free, stable, predictable and rock solid.
4 comments
1 u/derram 12 Aug 2017 17:20
https://hooktube.com/watch?v=phi_vUKGbuE?t=2h59m30s :
This has been an automated message.
0 u/10148176 12 Aug 2017 19:25
why are exceptions bad? they seem to be useful, although i don't use them that often. i really dont want to watch the whole video to figure out why you should not use exceptions
0 u/DukeofAnarchy [OP] 12 Aug 2017 20:05
The youtube link should take you to 2:29:30, which is the relevant part of the video.
2 u/roznak 13 Aug 2017 22:58
Exceptions are first of all misused in software engineering. They assume that it is either good or bad (= trigger exception). The hard reality in software you have "good", "bad" and "exception"
"False" should never be used to trigger an exception. A False may be recoverable and therefore becomes true in the whole process.
"Exceptions" should only be used on the very extreme unlikely event that your software cannot handle it. It is a situation that should actually never ever happen. If you throw exceptions then you basic design is deeply flawed. And now I have upset probably 90% of the Millennials. But I don't care. It is time to bring back good coding.
Why do exceptions "appear" to be helpful: Simple hello world applications and enterprise code that what I cal only live in a flat 2D space. You can't create complex code when you use exceptions. You can't test your code when you use exceptions. You can't recover in a simple way when you use exceptions. Exceptions will jump at some random location in your code you cannot predict.
Exceptions cause more problems then what they try to solve. get rid of using exceptions in your code and learn to develop without exceptions and I guarantee you that your code will become near zero bug free, stable, predictable and rock solid.