Go's error handling reminds me of C or PHP error handling. Check the status code. Since everything can mess with that error condition, you have to be careful in how you handle it, but there is nothing forcing you to handle it. I like exceptions because handling an error is default delegated until something wants to or can handle the error. In the case of go, if there is a layer above your function that should process the error, you have to do that if/err in each function that isn't going to handle it. I strongly believe in halting on error as the default response, and unwinding until the correct layer can proceed.
Especially true as API design seems to have moved away from using exceptions in non-exceptional situations; handling them locally is not desirable in most cases. In the old days we'd have a Parse method that would blow up the program if your string had characters other than digits; now we have a TryParse that returns e.g. an option type. It could also be because of the industry I'm in, but I've written (and read) extremely little exception-handling code in the last few years, because a real exception is not something my little domain method can do anything about.
That said, exception handling syntax is ugly and cumbersome in most languages I've seen. Whether it's try/catch/finally with braces or begin/rescue/ensure/end or whatever. It's also rarely written in a way that tells the reader where exactly the exceptions come from, it's just a blanket for a large block of code.
Something that ties the handling directly to the statement that breaks, without the noise of including the 'exceptional' behavior alongside the main logic, might be an improvement:
result = do_something(x, y, z)
handle SomeArgumentError with my_nre_handler(x, y, z)
handle RecordNotFound with missing_record_handler(x)
I may simply go back to Windows at home if that's the case, and will use a Windows Laptop at work if possible. Seriously, fuck Apple for this arrogance.
I've had devices from from Dell, Microsoft (3x), and Lenovo (2x) in the past few years, and they've all had hardware or driver issues either from the start or within the first few months. Tried countless registry hacks and driver reinstallations, spent dozens more hours on the phone with support reps who have no idea what they're doing, finally gotten a replacement but it doesn't include warranty coverage so the next failure is game over. Worst support by far was Dell -- they refuse to admit there's a problem, transfer you to wrong departments, and just wait for you to hang up. Their basic warranty coverage also only includes "depot service", which means you mail the machine away for two weeks and literally all they do is wipe it and reinstall the OS. Lenovo sent somebody to my home and actually resolved the issue.
Even when the system is put together correctly, every Windows update breaks something, or reverts some setting to a default value, and you don't get to choose which ones you need and which to skip. That Persian calendar fix is going to break your touchpad. Your system event log will be full of errors, and you won't know if you should be concerned. But that's just how Windows is, rotted and barely clunking along. Not to mention the built-in app ecosystem -- my wife tried their Mail app for a while, and one day it deleted all of her emails and calendar events. OneDrive sucks. Everything about Windows sucks.
I've done the "Reset This PC" thing on 3 different machines, and it's bricked all of them.
By contrast, the MacBook Pro that I've used at work for a few years has had zero problems and the OS feels so much more coherent. I do passionately hate the touch bar; I accidentally brush it all the time and suddenly the volume changes or Siri pops up or whatever irritating thing. I miss having a real Esc (yes, I've remapped Caps Lock, but muscle memory dies hard).
I've always used Windows laptops, but recently I've realized the MacBook is actually not more expensive after you factor in the hours of maintenance and the fact that Windows machines will die much more quickly no matter what you do.