Marcus Stade

> If you need to force async operations but don't care about the outcome you do end up sticking in a no-op fn, but I assume the engine would optimize...

It's not at all unheard of; jQuery for instance does this all the time with thing like getter/setter methods. Cases in point: the [data method](http://api.jquery.com/data/), [css method](http://api.jquery.com/css/), [attr method](http://api.jquery.com/attr/)... I...

@Schoonology – I don't disagree at all, it changes the _mechanics_ but not the _semantics_. This was the point I was trying to make. I think with your example you're...

I agree both of you, @tivac and @arturadib – it makes sense for the default to be sync given the context (i.e. shell scripting.) As for the API, I don't...

> I realize this may only prolong the discussion, but what about following nodejs' lead and making new commands for the new behaviors? Seeing as this issue has been open...

+1 – a consistent error object with codes or some such would be amazing. Should this actually be a feature of RethinkDB though?

Use `undefined` instead of `null` perhaps?

Sure, but what I mean is why not just set your values to `undefined` if you want defaults? This seems a bit magical to me; `null` is a value after...

Ah I see! Ok, let me see if we can just update the version of Electron we use, sounds like that might fix the problem. Will report back ASAP!

Sorry for the delay in getting back to you. I've just tried updating to the latest Electron version, which it the time of writing is 8.1.1, and according to the...