Re:A new approach to error handling
by zokier on Tuesday July 30, 2024 @02:47PM
(#41112775)
Maybe it's just me, but the benefits of implicit error handling in these examples seem really minor. Is it really worthwhile to have that as a feature just to save few ? in the function body?
[ Parent
| on HN ]
It didn't exist originally, but for high level programs like a TODO app that is mostly html templates, those question marks really don't add much value. Plus every time I showed code snippets to web developers, they got hung op on them.
Also, I wrote Go for like a decade, I love the explicitness of Go's error handling, but I still hate the `if err != nil {...}` checks.
Another reason was that Boomla will have a complete nocode UI, and I really don't want to clutter it up with explicit error handling.
That said, it's still an experiment, I guess.