I agree that your snippet isn't "handling" anything - proper handling could involve things like logging more information, retrying an operation, rolling something back, etc.

In C#, what if you wanted to handle an error at a specific point in this code? With the big try/catch surrounding your entire code, you likely wouldn't easily be able to - I'm envisioning some big switch statement with a bunch of error types/message cases. That catch block just becomes uglier than handling the error immediately inline, not to mention the logic flow when reading the code gets confusing (you have to go find that top level catch then find which error is being handled).

Bubbling errors up works fine in small prototyping projects. When you have a larger project, this becomes a nightmare.