Great! Now there are three different ways to call this API! Just because one dude has a different preferred coding style...
Now, arguably the original API wasn’t the best, but this is really not the way to design an API. There should preferably only be one way to do things and consistency with the rest of the library should be kept. Finally, don’t forget about browser compatibility.
As many others already argued, the root cause can be solved with just a sprinkle of syntax sugar to aid with try/catch.
Now, arguably the original API wasn’t the best, but this is really not the way to design an API. There should preferably only be one way to do things and consistency with the rest of the library should be kept. Finally, don’t forget about browser compatibility.
As many others already argued, the root cause can be solved with just a sprinkle of syntax sugar to aid with try/catch.