Paulo Cesar

@Phaiax can you merge the #64 PR and release the package on Package Control under a new name?

@Phaiax thanks, that would be great :+1:

whats the problem of wrapping it in your own method? I think that's out of the scope of this library (callbacks, events and such) ``` js objectPath.cget = function(obj, path,...

well, not everything that uses a callback is "async" (most Array prototype functions aren't, like sort, map, forEach, etc), they "block" further code execution and if they throw, they break...

well, just like `Array.prototype.forEach`, the array can be walked using loops just fine, or be wrapped inside a generator and iterated. I/O operations should never be synchronous, node has those...

use an array path when you expect no conversions. by convention, when there's a number in a string path, it always mean an array index. so in your example: ```js...

yes, anything that isEmpty return as true

there's an edge case where there is no check, like `objectPath.get(obj, [undefined])`, the array isn't empty, but the path is invalid... and going further, passing anything else isn't an object...

the benefits of throwing is that you can mix, besides the obvious stack trace that helps a ton in debugging, you can catch them either in try / catch (including...

but why would you be oblivious why your code is not executing? not everyone make testable code or rely solely on console.log for debugging. people tend to be pretty sloppy...