4 ms·
I'm talking about chrome's extension library returning NULL instead of a "tab" object when creating a new tab because of a syntax error in a completely differen
by such_a_casual 11y ago
I'm talking about chrome's extension library returning NULL instead of a "tab" object when creating a new tab because of a syntax error in a completely different file.
- pluma 11y agoYou're judging JavaScript by Chrome's extension API?
- such_a_casual 11y agoIt had nothing to do with Chrome's extension API. The API works perfectly fine. It has to do with the nature of JavaScript where syntax errors are "forgiven" leading to unforgivable bugs that require line by line review unless you use a tool to check your syntax. This was not the first, last, or only syntax caused bug I experienced. It was simply the most frustrating and inexplicable.
- pluma 11y agoSyntax errors in JS throw exceptions. JS syntax tends to hide certain mistakes but errors always throw. If Chrome's extension API swallows exceptions, that's not a JS problem.